Method and apparatus for pushing notification, mobile terminal, and graphical user interface

ABSTRACT

According to a method for pushing a notification provided in some embodiments of the present disclosure, a to-be-notified event is obtained; a first notification condition and a second notification condition are determined; a first notification page is displayed on the display when the first notification condition is met, to display, to a user, first association information when the first notification condition is met, for example, event status information, to-be-executed behavior information, and operation association information; and a second notification page is displayed on the display when the second notification condition is met after the first notification page is displayed, to display, to the user, second association information when the second notification condition is met. A plurality of notification pages are pushed for a to-be-notified event, and each notification page is pushed when a notification condition is met as the event develops.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/331,961, filed on Mar. 8, 2019, which is a National Stage filing ofInternational Application No. PCT/CN2016/098627, filed on Sep. 9, 2016.Both of the aforementioned applications are hereby incorporated byreference in their entireties.

TECHNICAL FIELD

The present disclosure relates to the computer field, and in particular,to a method, an apparatus, a mobile terminal, and a graphical userinterface for pushing a notification.

BACKGROUND

A mobile phone information notification is a basic function of a currentsmartphone, and is used to remind a user that there is a new instantmessage or a new event. For example, when a user successfully reserves ahotel room or a movie ticket, a mobile phone receives reservationsuccess notification information that is sent by a corresponding hotelor movie service provider and that is provided to the user; or when auser submits a taxi request and the request is accepted, a mobile phonereceives vehicle information that is sent by a corresponding vehicleservice provider and that is provided to the user.

In the prior art, mobile phone information notifications are all basedon a service application. When an event occurs in the serviceapplication, a notification pops up on the top of a mobile phone screen,or a notification is displayed in a strip form in the middle of a lockscreen, or a notification is displayed on a notification bar. Thenotification is retained if a user has not tapped the notification. Allthese notifications are used by the service application to simply notifythe user of what happened, and the notification ends after the user tapsor pulls down the notification to enter the application or performsimple interaction, for example, make an SMS reply.

During actual use of the user, when the user needs to view content inthese notifications, the user needs to manually search a correspondingmobile phone application or SMS message list for details. For example, auser reserves a flight ticket one week in advance, and receivesinformation such as a flight number and a departure time during thereservation. When the user wants to search for the information on theday of departure, the user needs to search a large quantity ofnotification SMS messages or a corresponding mobile phone applicationfor the information. Consequently, operations are complex, and it isrelatively difficult to obtain the information. Therefore, in the priorart, a notification can be pushed based on only simple content of aservice application, and the notification cannot be pushed based on aservice status change, in other words, a push manner is undiversified.

SUMMARY

A method for pushing a notification on a terminal device with a screenprovided in some embodiments is intended to resolve a prior-art problemthat a notification push manner is lack of variety ways.

According to a first aspect of the present disclosure, a method forpushing a notification on a terminal device with a screen is provided.The method includes: obtaining a to-be-notified event; determining afirst notification condition and a second notification condition basedon the to-be-notified event, where the to-be-notified event is an eventfor which a notification needs to be sent to a user, and the firstnotification condition and the second notification condition eachinclude at least any one of the following: a time condition, a placecondition, a user behavior condition, and an environment condition;displaying a first notification page when the first notificationcondition is met, where the first notification page is used to displayfirst association information of the to-be-notified event, and the firstassociation information includes one or more of event statusinformation, to-be-executed behavior information, and operationassociation information of the to-be-notified event when the firstnotification condition is met; and displaying a second notification pagewhen the second notification condition is met after the firstnotification page is displayed, where the second notification page isused to display second association information of the to-be-notifiedevent, and the second association information includes one or more ofevent status information, to-be-executed behavior information, andoperation association information of the to-be-notified event when thesecond notification condition is met.

In the prior art, a notification can be pushed based on only simplecontent of a service application. In comparison, in the pushnotification method in some embodiments, a plurality of notificationconditions are determined based on a to-be-notified event, acorresponding notification page is pushed when a notification conditionis met as the event develops, and content of the notification pageincludes various types of association information when the notificationcondition is met. Therefore, notification content corresponding todifferent event development stages of a to-be-notified event can bepushed to the user at the stages in a timely manner. In this way,notification manners are more diversified and effective.

According to some embodiments, the step of obtaining a to-be-notifiedevent includes: obtaining a push message and/or a user operation record;and analyzing whether content of the push message and/or the useroperation record is related to a to-be-notified event, and if yes,determining the to-be-notified event.

According to some embodiments, the mobile terminal may separately obtainthe push message or the user operation record, or may concurrentlyobtain the push message and the user operation record.

According to some embodiments, the mobile terminal may monitor, in realtime in background, whether a new push message is received, or monitor auser operation record in real time within the scope of permission, andwhen a to-be-notified event is determined in a push message or a useroperation record, trigger a subsequent step to be performed in a timelymanner to implement real-time message pushing.

According to some embodiments, in the method, the push message and/orthe user operation record are or is obtained, and event information ofthe to-be-notified event is collected. This does not totally rely on athird-party application, and the collected information is richer andmore comprehensive, so that subsequent context analysis can be made moreaccurately for the to-be-notified event.

According to some embodiments, the step of determining a firstnotification condition and a second notification condition based on theto-be-notified event includes: determining an event type of theto-be-notified event; determining a first notification node and a secondnotification node of the to-be-notified event based on the event type;collecting event information of the to-be-notified event based on theevent type; determining a node parameter of the first notification nodein the event information, to determine the first notification conditioncorresponding to the first notification node; and determining a nodeparameter of the second notification node in the event information, todetermine the second notification condition corresponding to the secondnotification node.

According to some embodiments, the step of displaying a firstnotification page when the first notification condition is met includes:monitoring a corresponding first condition parameter based on the firstnotification condition, where the first condition parameter includes atleast any one of the following: a current time, a current place, currentuser behavior information, and current environment information; anddisplaying the first notification page when the first conditionparameter meets the first notification condition.

According to some embodiments, the step of displaying a firstnotification page when the first notification condition is met includes:displaying a notification SMS message about the first notification pagewhen the first notification condition is met; and displaying the firstnotification page through jumping in response to a case in which anoperation input for the notification SMS message is detected.

According to some embodiments, the step of displaying a secondnotification page when the second notification condition is met afterthe first notification page is displayed includes: updating anddisplaying the second notification page based on the first notificationpage when the second notification condition is met after the firstnotification page is displayed.

According to some embodiments, the step of displaying a secondnotification page when the second notification condition is met afterthe first notification page is displayed further includes: deleting thefirst notification page after the second notification page is updatedand displayed based on the first notification page.

According to some embodiments, the method further includes: obtaining anupdate event of the to-be-notified event; updating the firstnotification condition and/or the second notification condition based onthe update event; and updating the corresponding currently displayedfirst notification page and/or the corresponding currently displayedsecond notification page based on the updated first notificationcondition and/or the updated second notification condition.

According to some embodiments, the step of displaying a firstnotification page on the display includes: displaying a notificationinterface on the display, where the first notification page exists inthe notification interface in a form of a subpage; displaying, in thenotification interface, a notification classification identifiercorresponding to the first notification page; and in response to a casein which an operation input for the notification classificationidentifier is detected, displaying, in the notification interface, thefirst notification page corresponding to the notification classificationidentifier, and hiding another subpage of the notification interface.

Likewise, the step of displaying a second notification page on thedisplay includes: displaying a notification interface on the display,where the second notification page exists in the notification interfacein a form of a subpage; displaying, in the notification interface, anotification classification identifier corresponding to the secondnotification page; and in response to a case in which an operation inputfor the notification classification identifier is detected, displaying,in the notification interface, the second notification pagecorresponding to the notification classification identifier, and hidinganother subpage of the notification interface.

According to some embodiments, the notification classificationidentifier is a notification list or a classification icon.

According to some embodiments, the notification interface is a lockscreen.

According to some embodiments, the method further includes: determininga notification cleaning condition based on the to-be-notified event,where the notification cleaning condition includes at least any one ofthe following: a cleaning time condition, a cleaning place condition,and a cleaning user behavior condition; and deleting the currentlydisplayed first notification page or the currently displayed secondnotification page of the to-be-notified event when the notificationcleaning condition is met.

Compared with a notification manner in the prior art, in the methodprovided in some embodiments of the present disclosure, eachnotification condition of a to-be-notified event is determined; eventinformation of the to-be-notified event is collected; it is determined,based on context analysis on the event information, whether to trigger anotification to be pushed to a user; and association information ofevent details related to the event information is updated to anotification interface in full screen in a form of an event display pagewhen it is determined that a notification needs to be pushed.Specifically, an existing event display page is updated or a newnotification page is created depends on whether the notificationinterface includes a corresponding notification page. In this way, whenthe event changes, the user can obtain a notification in a timelymanner, and conveniently obtain notification details of the event from acorresponding notification page in the notification interface based on auser requirement, without further searching an SMS message or anapplication.

According to a second aspect of the present disclosure, an apparatus forpushing a notification on a mobile terminal is provided. The apparatusincludes: an obtaining module, configured to obtain a to-be-notifiedevent, where the to-be-notified event is an event for which anotification needs to be pushed to a user; a determining module,configured to determine a first notification condition and a secondnotification condition based on the to-be-notified event, where theto-be-notified event is an event for which a notification needs to besent to the user, and the first notification condition and the secondnotification condition each include at least any one of the following: atime condition, a place condition, a user behavior condition, and anenvironment condition; a first display module, configured to display afirst notification page when the first notification condition is met,where the first notification page is used to display first associationinformation of the to-be-notified event, and the first associationinformation includes one or more of event status information,to-be-executed behavior information, and operation associationinformation of the to-be-notified event when the first notificationcondition is met; and a second display module, configured to display asecond notification page when the second notification condition is metafter the first notification page is displayed, where the secondnotification page is used to display second association information ofthe to-be-notified event, and the second association informationincludes one or more of event status information, to-be-executedbehavior information, and operation association information of theto-be-notified event when the second notification condition is met.

According to some embodiments, the obtaining module includes: anobtaining submodule, configured to obtain a push message and/or a useroperation record; and an analysis submodule, configured to: analyzewhether content of the push message and/or the user operation record isrelated to a to-be-notified event, and if yes, determine theto-be-notified event.

According to some embodiments, the determining module includes: a typedetermining submodule, configured to determine an event type of theto-be-notified event; a node determining submodule, configured todetermine a first notification node and a second notification node ofthe to-be-notified event based on the event type; an informationdetermining submodule, configured to collect event information of theto-be-notified event based on the event type; a parameter determiningsubmodule, configured to determine a node parameter of the firstnotification node in the event information, to determine the firstnotification condition corresponding to the first notification node; anda condition determining submodule, configured to determine a nodeparameter of the second notification node in the event information, todetermine the second notification condition corresponding to the secondnotification node.

According to some embodiments, the first display module includes: afirst monitoring submodule, configured to monitor a corresponding firstcondition parameter based on the first notification condition, where thefirst condition parameter includes at least any one of the following: acurrent time, a current place, current user behavior information, andcurrent environment information; and a first display submodule,configured to display the first notification page when the firstcondition parameter meets the first notification condition.

According to some embodiments, the first display module includes: asecond display submodule, configured to display a notification SMSmessage about the first notification page when the first notificationcondition is met; and a third display submodule, configured to displaythe first notification page through jumping in response to a case inwhich an operation input for the notification SMS message is detected.

According to some embodiments, the second display module includes anupdate submodule, configured to update and display the secondnotification page based on the first notification page when the secondnotification condition is met after the first notification page isdisplayed.

According to some embodiments, the second display module furtherincludes a deletion submodule, configured to delete the firstnotification page after the second notification page is updated anddisplayed based on the first notification page.

According to some embodiments, the apparatus further includes: an eventupdate module, configured to obtain an update event of theto-be-notified event; a condition update module, configured to updatethe first notification condition and/or the second notificationcondition based on the update event; and a page update module,configured to update the corresponding currently displayed firstnotification page and/or the corresponding currently displayed secondnotification page based on the updated first notification conditionand/or the updated second notification condition.

According to some embodiments, the first display module includes: afirst interface display submodule, configured to display a notificationinterface on the display, where the first notification page exists inthe notification interface in a form of a subpage; a first identifierdisplay submodule, configured to display, in the notification interface,a notification classification identifier corresponding to the firstnotification page; and a first page display submodule, configured to: inresponse to a case in which an operation input for the notificationclassification identifier is detected, display, in the notificationinterface, the first notification page corresponding to the notificationclassification identifier, and hide another subpage of the notificationinterface.

According to some embodiments, the second display module includes asecond interface display submodule, a second identifier displaysubmodule, and a second page display submodule. The second interfacedisplay submodule displays a notification interface on the display,where the second notification page exists in the notification interfacein a form of a subpage. The second identifier display submoduledisplays, in the notification interface, a notification classificationidentifier corresponding to the second notification page. In response toa case in which an operation input for the notification classificationidentifier is detected, the second page display submodule displays, inthe notification interface, the second notification page correspondingto the notification classification identifier, and hides another subpageof the notification interface.

According to some embodiments, the notification classificationidentifier is a notification list or a classification icon.

According to some embodiments, the notification interface is a lockscreen.

According to some embodiments, the apparatus further includes: a firstcleaning module, configured to determine a notification cleaningcondition based on the to-be-notified event, where the notificationcleaning condition includes at least any one of the following: acleaning time condition, a cleaning place condition, and a cleaning userbehavior condition; and a second cleaning module, configured to deletethe currently displayed first notification page or the currentlydisplayed second notification page of the to-be-notified event when thenotification cleaning condition is met.

In some embodiments, the display includes a touch-sensitive surface anda screen.

According to a third aspect, a mobile terminal provided in someembodiments of the present disclosure includes: a display, where thedisplay includes a touch-sensitive surface and a screen; one or moreprocessors; a memory; a plurality of application programs; and one ormore programs, where the one or more programs are stored in the memoryand configured to be executed by the one or more processors, the one ormore programs include an instruction, and the instruction is used toobtain a to-be-notified event, where the to-be-notified event is anevent for which a notification needs to be pushed to a user.

In some specific implementations, the terminal can perform a procedurebased on the method provided in the embodiments of the presentdisclosure in the first aspect.

According to a fourth aspect, some embodiments of the present disclosureprovide a graphical user interface on a mobile terminal with a displayapparatus. The graphical user interface includes a notificationinterface displayed on the display apparatus, where a first notificationpage is displayed in the notification interface in response to a case inwhich a first notification condition of a to-be-notified event is met,where the first notification page is used to display first associationinformation of the to-be-notified event, the to-be-notified event is anevent for which a notification needs to be sent to a user, and the firstassociation information includes one or more of event statusinformation, to-be-executed behavior information, and operationassociation information of the to-be-notified event when the firstnotification condition is met; and after the first notification page isdisplayed, a second notification page is displayed in the notificationinterface in response to a case in which a second notification conditionof the to-be-notified event is met, where the second notification pageis used to display second association information of the to-be-notifiedevent, the second association information includes one or more of eventstatus information, to-be-executed behavior information, and operationassociation information of the to-be-notified event when the secondnotification condition is met, and the first notification condition andthe second notification condition each include at least any one of thefollowing: a time condition, a place condition, a user behaviorcondition, and an environment condition.

According to some embodiments, in a process of displaying the firstnotification page in the notification interface in response to the casein which the first notification condition of the to-be-notified event ismet, the user interface includes: a notification SMS message about thefirst notification page is displayed in response to the case in whichthe first notification condition of the to-be-notified event is met; andthe first notification page is displayed through jumping in thenotification interface in response to a case in which an operation inputfor the notification SMS message is detected.

According to some embodiments, the notification interface includes thefirst notification page and/or the second notification page, thenotification interface further includes a notification classificationidentifier, and the first notification page or the second notificationpage corresponding to an operation input of the user for thenotification classification identifier is displayed through jumping inresponse to the operation input.

According to some embodiments, the notification classificationidentifier is a notification list or a classification icon.

According to some embodiments, the notification interface is a lockscreen.

BRIEF DESCRIPTION OF DRAWINGS

To describe the technical solutions in the embodiments of the presentdisclosure more clearly, the following briefly describes theaccompanying drawings required for describing the embodiments.Apparently, the accompanying drawings in the following description showmerely some but not all the embodiments of the present disclosure.Persons of ordinary skill in the art may derive other drawings fromthese accompanying drawings without creative efforts.

FIG. 1 is a schematic structural diagram of a terminal for pushing anotification according to some embodiments;

FIG. 2 is a schematic flowchart of pushing a notification on a mobileterminal device according to some embodiments;

FIG. 3 is a schematic structural diagram of an apparatus for pushing anotification according to some embodiments;

FIG. 4(a) to FIG. 4(h) are schematic diagrams of an interface forpushing a notification according to several embodiments of some specificscenarios;

FIG. 5(a) to FIG. 5(c) are schematic diagrams of an interface forpushing a notification in a current display interface in an unlockedstate according to some embodiments;

FIG. 5(d) to FIG. 5(h) are schematic diagrams of an interface forpushing a notification on a lock screen according to some embodiments;

FIG. 5(i) to FIG. 5(l) are schematic diagrams of an interface forpushing a notification on a lock screen according to some embodiments;

FIG. 6 is a schematic structural diagram of a data engine for pushing anotification according to an embodiment of some specific scenarios;

FIG. 7A and FIG. 7B are a schematic flowchart of pushing a notificationaccording to an embodiment of some specific scenarios;

FIG. 8(a) to FIG. 8(h) are schematic diagrams of an interface forpushing a notification at each stage according to embodiments of somespecific scenarios;

FIG. 9(a) to FIG. 9(d) are schematic diagrams of an interface forpushing a notification at each stage according to embodiments of somespecific scenarios;

FIG. 10(a) to FIG. 10(e) are schematic diagrams of an interface forpushing a notification at each stage according to embodiments of somespecific scenarios;

FIG. 11(a) and FIG. 11(b) are schematic diagrams of an interface forpushing a notification at each stage according to embodiments of somespecific scenarios;

FIG. 12(a) to FIG. 12(e) are schematic diagrams of an interface forpushing a notification at each stage according to embodiments of somespecific scenarios;

FIG. 13(a) to FIG. 13(g) are schematic diagrams of an interface forpushing a notification at each stage according to embodiments of somespecific scenarios; and

FIG. 14(a) and FIG. 14(b) are schematic diagrams of an interface forpushing a notification at each stage according to embodiments of somespecific scenarios.

DESCRIPTION OF EMBODIMENTS

The following further describes the technical solutions in theembodiments of the present disclosure with reference to the accompanyingdrawings in the embodiments of the present disclosure.

Herein, a method and an apparatus for pushing a notification in thepresent disclosure may be applied to any mobile terminal with a displayapparatus and a plurality of application programs. The apparatus may behardware, software, or a combination of hardware and software with aprocessing capability installed on the mobile terminal. The mobileterminal may be a mobile phone, a tablet computer (Tablet PersonalComputer), a laptop computer (Laptop Computer), a digital camera, adigital video camera, a projection device, a personal digital assistant(personal digital assistant, PDA for short), an e-book reader (English:e-book reader), a wearable device (Wearable Device), a virtual realityintelligent device, or the like. The mobile terminal may establishcommunication with a network by using 2G 3G, 4G or a WLAN (wirelesslocal area network). For conciseness, this is not further limited in theembodiments of the present disclosure. For ease of description, a mobileterminal is used as an example for description in the followingembodiments.

Herein, the notification may also be referred to as a reminder, amessage, a reminder message, reminder information, or the like. Whenreceiving external new information or internally triggering a new event(for example, an alarm or a system reminder), the mobile terminalusually displays content of a related notification on a screen in atimely manner, or may push content of a notification to a user in atimely manner by using a voice reminder or a vibration reminder, or inanother manner.

An embodiment of the present disclosure provides a mobile terminal, andthe mobile terminal may be configured to perform the method described inthe foregoing embodiment of the present disclosure. FIG. 1 shows astructure of a mobile terminal 100 according to some embodiments of thepresent disclosure.

The mobile terminal may be a terminal device such as a mobile phone, atablet computer, a PDA (Personal Digital Assistant, personal digitalassistant), a POS (Point of Sale, point of sale), or an in-vehiclecomputer. For example, the mobile terminal is a mobile phone. FIG. 1 isa block diagram of a partial structure of a mobile phone 100 related tothe mobile terminal provided in the embodiments of the presentdisclosure. Referring to FIG. 1, the mobile phone 100 includescomponents such as an RF (Radio Frequency, radio frequency) circuit 110,a memory 120, an input unit 130, a display unit 140, a sensor 150, anaudio frequency circuit 160, a Wi-Fi (wireless fidelity, WirelessFidelity) module 170, a processor 180, and a power supply 190. Personsskilled in the art may understand that the mobile phone structure shownin FIG. 1 is merely an example of an implementation, and does notconstitute a limitation on the mobile phone. The mobile phone mayinclude more or fewer components than those shown in the figure, or acombination of some components, or differently disposed components.

Each constituent component of the mobile phone 100 is described indetail below with reference to FIG. 1.

The RF circuit 110 may be configured to receive and send information, orreceive and send a signal in a call process; particularly, afterreceiving downlink information of a base station, send the downlinkinformation to the processor 180 for processing; and in addition, sendrelated uplink data to the base station. Generally, the RF circuitincludes but is not limited to an antenna, at least one amplifier, atransceiver, a coupler, an LNA (Low Noise Amplifier, low noiseamplifier), a duplexer, and the like. In addition, the RF circuit 110may further communicate with a network and another device throughwireless communication. Any communication standard or protocol may beused for the wireless communication, and the communication standard orprotocol includes but is not limited to GSM (Global System for MobileCommunications, Global System for Mobile Communications), GPRS (GeneralPacket Radio Service, general packet radio service), CDMA (Code DivisionMultiple Access, Code Division Multiple Access), WCDMA (Wideband CodeDivision Multiple Access, Wideband Code Division Multiple Access), LTE(Long Term Evolution, Long Term Evolution), email, SMS (Short MessageService, short message service), and the like.

The memory 120 may be configured to store a software program and amodule. The processor 180 executes various functional applications anddata processing of the mobile phone 100 by running the software programand the module that are stored in the memory 120. The memory 120 maymainly include a program storage area and a data storage area. Theprogram storage area may store an operating system, an applicationprogram required by at least one function (such as a voice play functionor an image play function), and the like. The data storage area maystore data (such as audio data or an address book) that is created basedon use of the mobile phone 100, and the like. In addition, the memory120 may include a high-speed random access memory, and may furtherinclude a nonvolatile memory, for example, at least one magnetic diskstorage device, a flash storage device, or another volatile solid-statestorage device.

The input unit 130 may be configured to: receive entered digit orcharacter information, and generate a key signal input related to a usersetting and function control of the mobile phone 100. Specifically, theinput unit 130 may include a touch panel 131 and other input devices132. The touch panel 131, also referred to as a touchscreen, may collecta touch operation (for example, an operation performed by a user on ornear the touch panel 131 by using any proper object or accessory such asa finger or a stylus) of the user on or near the touch panel 131, anddrive a corresponding connection apparatus based on a preset program.Optionally, the touch panel 131 may include two parts: a touch detectionapparatus and a touch controller. The touch detection apparatus detectsa touch orientation of the user, detects a signal brought by the touchoperation, and transmits the signal to the touch controller. The touchcontroller receives touch information from the touch detectionapparatus, converts the touch information into touch point coordinates,and sends the touch point coordinates to the processor 180, and canreceive and execute a command sent by the processor 180. In addition,the touch panel 131 may be implemented by using a plurality of typessuch as a resistive type, a capacitive type, an infrared ray, and asurface acoustic wave. In addition to the touch panel 131, the inputunit 130 may include the other input devices 132. Specifically, theother input devices 132 may include but are not limited to one or moreof a physical keyboard, a function key (such as a volume control key oran on/off key), a trackball, a mouse, a joystick, and the like.

The display unit 140 may be configured to display information entered bythe user or information provided to the user and various menus of themobile phone 100. The display unit 140 may include a display panel 141.Optionally, the display panel 141 may be configured by using an LCD(Liquid Crystal Display, liquid crystal display), an OLED (OrganicLight-Emitting Diode, organic light-emitting diode), or the like.Further, the touch panel 131 may cover the display panel 141. Afterdetecting the touch operation on or near the touch panel 131, the touchpanel 131 transmits the touch operation to the processor 180 todetermine a type of a touch event, and then the processor 180 provides acorresponding visual output on the display panel 141 based on the typeof the touch event. Although the touch panel 131 and the display panel141 in FIG. 1 are used as two independent components to implement inputand input functions of the mobile phone 100, in some embodiments, thetouch panel 131 and the display panel 141 may be integrated to implementthe input and output functions of the mobile phone 100.

The mobile phone 100 may further include at least one sensor 150, forexample, a light sensor, a motion sensor, and another sensor.Specifically, the light sensor may include an ambient light sensor and aproximity sensor. The ambient light sensor may adjust luminance of thedisplay panel 141 based on brightness of ambient light. The proximitysensor may turn off the display panel 141 and/or backlight when themobile phone 100 approaches an ear. As a type of motion sensor, anaccelerometer sensor may detect a value of acceleration in eachdirection (usually on three axes), may detect a value and a direction ofgravity in a static state, and may be used in an application forrecognizing a mobile phone posture (such as screen switching between alandscape mode and a portrait mode, a related game, or magnetometerposture calibration), a function related to vibration recognition (suchas a pedometer or a knock), or the like. Another sensor such as agyroscope, a barometer, a hygrometer, a thermometer, or an infraredsensor may be further configured in the mobile phone 100. Details arenot described herein.

The audio frequency circuit 160, a speaker 161, and a microphone 162 mayprovide an audio interface between the user and the mobile phone 100.The audio frequency circuit 160 may convert received audio data into anelectrical signal, and transmit the electrical signal to the speaker161, and the speaker 161 converts the electrical signal into a soundsignal for output. In addition, the microphone 162 converts a collectedsound signal into an electrical signal. The audio frequency circuit 160receives the electrical signal, converts the electrical signal intoaudio data, and then outputs the audio data to the processor 180 forprocessing. The processor 180 sends the audio data to, for example,another mobile phone by using the RF circuit 110, or outputs the audiodata to the memory 120 for further processing.

Wi-Fi is a short-range wireless transmission technology. By using theWi-Fi module 170, the mobile phone 100 may help the user receive andsend an email, browse a web page, access streaming media, and so on. TheWi-Fi module 170 provides wireless broadband Internet access to theuser. Although FIG. 1 shows the Wi-Fi module 170, it may be understoodthat the Wi-Fi module 170 is not a mandatory part of the mobile phone100, and can be omitted based on a requirement without changing theessence of the present disclosure.

The processor 180 is a control center of the mobile phone 100, usesvarious interfaces and lines to connect all parts of the entire mobilephone, and performs various functions and data processing of the mobilephone 100 by running or executing the software program and/or the modulestored in the memory 120 and invoking data stored in the memory 120, toperform overall monitoring on the mobile phone. Optionally, theprocessor 180 may include one or more processing units. Preferably, anapplication processor and a modem processor may be integrated into theprocessor 180. The application processor mainly processes an operatingsystem, a user interface, an application program, and the like, and themodem processor mainly processes wireless communication. It may beunderstood that alternatively, the modem processor may not be integratedinto the processor 180.

The mobile phone 100 further includes the power supply 190 (such as abattery) that supplies power to each component. Preferably, the powersupply may be logically connected to the processor 180 by using a powersupply management system, thereby implementing functions such ascharging management, discharging management, and power consumptionmanagement by using the power supply management system.

The mobile phone 100 may further include a camera, a Bluetooth module,and the like although they are not shown. Details are not describedherein.

FIG. 2 shows a method for pushing a notification by a mobile terminalaccording to some embodiments. The mobile terminal pushes a notificationby performing at least the following steps: Step S201: Obtain ato-be-notified event for which a notification needs to be sent to auser. Step S202: Determine a first notification condition and a secondnotification condition based on the to-be-notified event. Step S203:Display a first notification page when the first notification conditionis met. Step S204: Display a second notification page when the secondnotification condition is met after the first notification page isdisplayed.

The first notification page is used to display first associationinformation of the to-be-notified event, the first associationinformation includes one or more of event status information,to-be-executed behavior information, and operation associationinformation of the to-be-notified event when the first notificationcondition is met, the second notification page is used to display secondassociation information of the to-be-notified event, and the secondassociation information includes one or more of event statusinformation, to-be-executed behavior information, and operationassociation information of the to-be-notified event when the secondnotification condition is met.

In the prior art, a notification can be pushed based on only simplecontent of a service application. In comparison, in the push method insome embodiments, a plurality of notification conditions are determinedbased on a to-be-notified event, a corresponding notification page ispushed when a notification condition is met as the event develops, andcontent of the notification page includes various types of associationinformation when the notification condition is met. Therefore,notification content corresponding to different event development stagesof a to-be-notified event can be pushed to the user at the stages in atimely manner, thereby improving notification effectiveness.

In the present disclosure, the to-be-notified event may be an event thatprogresses continuously and for which a corresponding reminder needs tobe provided to the user on a lock screen. In the method, as the eventprogresses continuously, the mobile terminal provides reminder contentabout the event to the user on the lock screen based on eventinformation of the to-be-notified event. At different stages, whendifferent notification conditions (for example, a time condition, aplace condition, a user behavior condition, and an environmentcondition) are met, reminder content provided by the mobile terminal tothe user on the lock screen or in another notification interface issomewhat different.

In step S201, the mobile terminal obtains a to-be-notified event.

In some embodiments, the step of obtaining a to-be-notified event mayinclude step S201 a and step S202 b. In step S201 a, the mobile terminalobtains a push message and/or a user operation record. In step S202 b,the mobile terminal analyzes whether content of the push message and/orthe user operation record is related to a to-be-notified event, and ifyes, the mobile terminal determines the to-be-notified event.

In some embodiments, the mobile terminal may communicate with theoutside by using the RF circuit 110 or the Wi-Fi module 170 to obtaininformation, and obtain the push message through analysis by using theprocessor 180. The mobile terminal may obtain an operation input signalof the user by using the input unit 130, the sensor 150, or the audiofrequency circuit 160, analyze the operation input signal by using theprocessor 180, and store the operation input signal in the useroperation record.

The mobile terminal may separately obtain the push message or the useroperation record, or may concurrently obtain the push message and theuser operation record. The mobile terminal may receive or activelycollect the push message and/or the user operation record, and this maybe performed in real time or performed periodically. A specificdetermining manner may be specifically determined based on conditionssuch as different scenario requirements or apparatus performance of themobile terminal. In some embodiments, the mobile terminal may monitor,in real time in background, whether a new push message is received, ormonitor a user operation record in real time within the scope ofpermission, and when a to-be-notified event is determined in a pushmessage or a user operation record, trigger a subsequent step to beperformed in a timely manner to implement real-time message pushing.

In some embodiments, the push message may be an SMS message, an email, acall, an application notification, or the like that is sent from theoutside and that is received by the mobile terminal. In someembodiments, the push message may be pushed by a service provider orthird-party application software. In some specific scenario embodiments,the service provider may be, for example, a ticket service provider (atrain ticket, a bus ticket, or a steamer ticket), a group buyingwebsite, a shopping website, a taxi service provider, a schedulemanagement service provider, or a travel management service provider,but is not limited thereto.

In some embodiments, the user operation record may be a user operationlog, and is used to record a user operation behavior. The user operationbehavior includes a purposeful operation behavior performed by the useron an input device of the mobile terminal, for example, a single or aseries of operations performed by the user on a touchscreen, or a voiceinstruction entered by the user on a microphone. In some specificscenario embodiments, the user operation behavior event may be that theuser performs an operation behavior in a third-party application, forexample, hails a taxi, reserves a train ticket, a bus ticket, a flightticket, a steamer ticket, a movie ticket, or a hotel room, or goesonline shopping. For example, the user taps and opens the third-partyapplication, and taps “Confirm the order”, “Submit the order”, or“Collect” for a selected target, or selects a shopping object on ashopping website, and correspondingly fills in express information,performs a payment operation, and so on. The third-party application isan application (APP, Application) that is installed on the mobileterminal and that provides a service by using a third-party serviceprovider.

Certainly, persons skilled in the art should understand that the pushmessage and the user operation behavior are examples that facilitatefurther understanding of persons skilled in the art, and are actuallynot limited to the foregoing examples. A push message and a useroperation behavior, for example, a push message provided in a virtualreality display manner and a user operation behavior obtained by themobile terminal by directly detecting a brain wave, are applicableprovided that the push message and the user operation behavior can beidentified by the mobile terminal by using the input device and theprocessor.

Then the mobile terminal analyzes the push message, the user operationrecord, or content of a combination of the two to determine whetherthere is a to-be-notified event.

In some embodiments, the mobile terminal searches the push message for aspecified keyword, key statement, key link, and key number, andspecified key semantics to determine whether the push message is relatedto a to-be-notified event.

In some specific scenario embodiments, when receiving a new message or anew email, the mobile terminal analyzes content of the new message orthe new email, and searches the new message or the new email for aspecified keyword, or makes semantic analysis. For example, the mobileterminal determines whether a number of an SMS message sender is anumber of a specified service provider or whether an email address of anemail sender is an email address of a specified service provider, andanalyzes whether content of the SMS message, the message, or the emailincludes notification content (for example, semantic content such as“The train ticket is successfully reserved”, “The order has been sent”,or “There is a response from a taxi for the order”) that meets anotification condition. Herein the specified service provider may bepredetermined for cooperation, or may be determined by learning a usagehabit or the like of the user. When learning through analysis thatcontent of a new SMS message includes semantics related to flight ticketreservation, for example, “issued”, “successfully reserved”, or“passenger”, the mobile terminal comprehensively infers that the reportevent information is a to-be-notified event about flight ticketreservation.

In some specific scenario embodiments, when receiving a new email, themobile terminal analyzes whether an email address of a sender of the newemail is an official service email address of a hotel, or makes semanticanalysis on email content of the new email, to determine whether thereport event is a service-type report event, for example, analyzeswhether there is content related to hotel reservation, for example,“hotel”, “successfully reversed”, or “guest”. The mobile terminaldetermines, based on the new email, that the report event is a hotelreservation event and meets a notification condition related to hotelreservation.

A specified keyword, key statement, key link, and key number, andspecified key semantics for determining whether a push message isrelated to a to-be-notified event may be preset, or may be collected,created, or updated through machine learning based on a behavior habitand a usage habit of the user. In some specific scenario embodiments, ifthe user frequently performs a group buying reservation behavior,information such as a notification condition of a group buyingreservation event is created based on the group buying reservationbehavior frequently performed by the user, including using, asnotification conditions for subsequently determining whether a reportevent is a to-be-notified event about group buying reservation, a numberof a group buying service provider for pushing an SMS message, an emailaddress of the group buying service provider for pushing an email, andcontent logic of a group buying reservation message.

In some embodiments, the mobile terminal analyzes a user operationbehavior from the user operation record to determine whether the useroperation behavior is related to a to-be-notified event.

In some specific embodiments, the mobile terminal learns, throughanalysis from the user operation record, a related operation performedby the user in a specified third-party application (a related operationperformed in an application such as a taxi hailing application, a ticketapplication (a vehicle ticket, a flight ticket, or a movie ticket), aweather application, a music application, a group buying application, ora travel application), learns through analysis that the user requests arelated service from the specified third-party application and confirmsthe related service, and determines that the related service is to occursubsequently and needs to be notified to the user at a correspondingoccurrence node. In this case, the mobile terminal determines that thereport event is a to-be-notified event. For example, if the user tapsand opens the third-party application, and correspondingly fills inexpress information, performs a payment operation, and so on for aselected target, it is determined that the report event is ato-be-notified event about online shopping.

In some embodiments, the mobile terminal may obtain the user operationbehavior event by reading the user operation record. The mobile terminalmay analyze a series of operations of the user from the user operationrecord, to determine the user operation behavior event. When the usertaps an application icon on a screen of a screen desktop, it indicatesthat the user requests to open application software corresponding to theapplication icon. After the application software is opened, the userperforms corresponding operations such as tapping, flicking, and voiceinput in an interface of the application software. In this case, theapplication software may determine, based on the series of operations ofthe user, that the user performs events such as reservation, collection,and forwarding. The user operation behavior event may be, for example,an event including a single operation or a series of operationsperformed by the user on the touchscreen of the mobile terminal.

In step S202, the mobile terminal determines a first notificationcondition and a second notification condition based on theto-be-notified event.

In some embodiments, step S202 further includes step S202 a, step S202b, step S202 c, step S202 d, and step S202 e. In step S202 a, the mobileterminal determines an event type of the to-be-notified event. In stepS202 b, the mobile terminal determines a first notification node and asecond notification node of the to-be-notified event based on the eventtype. In step S202 c, event information of the to-be-notified event iscollected based on the event type. In step S202 d and step S202 e, anode parameter of the first notification node is determined in the eventinformation, to determine the first notification condition correspondingto the first notification node, and a node parameter of the secondnotification node is determined in the event information, to determinethe second notification condition corresponding to the secondnotification node.

In some embodiments, the mobile terminal analyzes the push message, theuser operation record, or content of a combination of the two todetermine the event type of the to-be-notified event, and determines thefirst notification node and the second notification node of theto-be-notified event based on the event type.

In some embodiments, the event type is a service type, and the servicetype may be preset. In some specific scenario embodiments, the servicetype may be obtained through classification based on a specific servicesuch as hotel reservation, flight ticket reservation, vehicle ticketreservation, an express service, or a group buying service.To-be-notified events of each service type have approximately same eventlogic and several event nodes, and have several correspondingnotification conditions (including a time condition, a place condition,a user behavior condition, an environment condition, and the like).Specific parameters of several notification conditions of eachto-be-notified event need to be determined based on specific eventinformation of the to-be-notified event. For example, notification nodesof a to-be-notified event about vehicle ticket reservation include atleast a departure notification node and an arrival notification node,but specific parameters such as a specific departure time and place anda specific arrival time and place need to be further determined based onevent information of vehicle ticket reservation.

Then the mobile terminal collects the event information of theto-be-notified event based on the event type. In some embodiments, themobile terminal may collect related event information from a historicalrecord. In some embodiments, the historical record includes any one or acombination of the following: an SMS message, an email, an address book,a voice record, a notepad record, a to-do list on a calendar, and a pushmessage of a third-party application. For example, the mobile terminalscans data stored on the mobile terminal, and collects the eventinformation of the report event from the existing SMS message, email,call record, voice record, notepad content, to-do list on the calendar,push message of the third-party application, and the like; or directlyobtains the corresponding event information from the third-partyapplication or a third-party service website based on data obtainingpermission; or searches, based on a user operation behavior log, for aselection operation performed by the user in the third-partyapplication, and the like, and collects the event information from apage related to the selection operation.

In some specific scenario embodiments, the event information may includean occurrence time, an occurrence place, associated-person information,service content information, and the like of the event. For example,time information of a flight ticket reservation event includes adeparture time, an arrival time, a departure place, and an arrival placeof an airplane, a name, an identity card number, and a passport numberof a passenger, and the like. Service content information includesinformation about all stages. For example, flight ticket related eventsinclude check-in, departure, arrival at an airport, luggage storage, andthe like. In addition, service content information may be a hotelrelated event, including preparing to check in, providing an unlockingkey, and the like. A train ticket related event may include “waiting”,“about to set off”, “about to arrive”, and the like. A movie ticketrelated event may include sequence number redemption, seat guidance, andthe like. An express related event may include “collected”, “beingdelivered”, “to be picked up”, “signed”, and the like. A taxi hailingrelated event may include “prepare to dispatch a taxi”, “driver setsoff”, “taxi arrives”, “travel starts”, “to pay”, and the like.

For example, for a to-be-notified event about hotel reservation, themobile terminal logs in, based on a service type of the hotelreservation, from background to a third-party application related to ahotel reservation event, collects service related information of thehotel reservation event, or collects service related information from anew corresponding email based on the hotel reservation event, where theservice related information includes a hotel check-in time, a hotelname, a guest name, a type of a reserved room, a fee, and the like, andsearches the third-party application for a corresponding hotel orderbased on known information about the hotel reservation event such as areservation event and hotel check-in, to further obtain relatedinformation such as a hotel address, hotel star-level information, ahotel check-in notice, and a nearby public transportation guide to ahotel, so as to obtain event information of the hotel reservation event.

In step S202 d or step 202 e, the mobile terminal obtains the nodeparameters of the notification nodes (the first notification node andthe second notification node) from the event information based on thenotification nodes of the to-be-notified event, and determinesnotification conditions (the first notification condition and the secondnotification condition) of the notification nodes based on a combinationof the node parameters.

In some embodiments, a node parameter of each notification node may be atime parameter, a place parameter, an environment parameter, a userbehavior parameter, a hardware parameter, or a combination thereof. Forexample, internal timing is used as a preset notification conditionbased on the event information, and a notification is triggered by anevent based on the timing. The environment parameter may include anenvironment temperature, environment pressure, environment brightness,gravity, a speed, a posture, and the like. The user behavior parameterincludes user usage frequency information, user registrationinformation, user motion information, and the like. The hardwareparameter may include a hardware status, a software status, and the likeof the mobile terminal.

In some specific scenario embodiments, for a to-be-notified event abouthotel reservation, it is determined, based on a check-in date and areminder advance such as a one-day advance, that a first notificationcondition is to provide a reminder one day before the actual check-indate (reminder content corresponding to the first notification conditionis related information indicating that the user is to have a stay in ahotel), and a second notification condition is to provide a reminder ata specific time on the actual check-in date (reminder contentcorresponding to the second notification condition includes relatedinformation indicating that the user is to check in).

In step S203, after determining the notification conditions, the mobileterminal first monitors a corresponding first condition parameter basedon the first notification condition.

Step S203 includes step S203 a and step S203 b. In step S203 a, themobile terminal monitors the corresponding first condition parameterbased on the first notification condition, where the first conditionparameter includes at least any one of the following: a current time, acurrent place, current user behavior information, and currentenvironment information. In step S203 b, when the first conditionparameter meets the first notification condition, the first notificationpage is displayed.

The first condition parameter is a real-time parameter valuecorresponding to the node parameter of the first notification condition,and includes the current time, the current place, the current userbehavior information, and the current environment information. Forexample, the current time is 8:00 a.m., the current place is home, thecurrent user behavior information is a running state, and the currentenvironment information is raining.

The mobile terminal may collect the corresponding first conditionparameter in the background. In some embodiments, the mobile terminalobtains the current time by using a clock of the mobile terminal,determines the current place by using a GPS, Wi-Fi, an operator network,and the like, and obtains a current temperature, pressure, currentbrightness, and the like by using various sensing apparatuses. Thecurrent user behavior information may include an operation performed bythe user on third-party software, an operation performed on notificationinformation on the lock screen, a user motion behavior, and the like.The user behavior information may be obtained by monitoring a useroperation behavior, for example, monitoring current interfaceinformation and an operation performed by the user on the touchscreen,or may be obtained by using various sensors of the mobile terminal. Forexample, a motion behavior such as a speed and a posture of the user isobtained by using a gravity sensor, an inertial sensor (including agyroscope, an acceleration sensor, and the like), and the like. Forexample, a current speed, a posture, gravity, and the like may beobtained by using a sensing apparatus (for example, a gyroscope).

In addition, the mobile apparatus may further monitor current hardwarestatus information, including a hardware temperature, hardware CPU(central processing unit, Central Processing Unit) usage, and the like.The mobile apparatus may obtain an apparatus hardware status by usingcorresponding monitoring software.

The first notification page including first association information isdisplayed when the first notification condition is met. The firstassociation information includes any one or a combination of eventstatus information, to-be-executed behavior information, and operationassociation information. Preferably, the event status information, theto-be-executed behavior information, and the operation associationinformation are all displayed on the first notification page.

In some embodiments, the event status information includes informationabout a current event node of the to-be-notified event, event start andend time information, event start and end place information, characterinformation, environment information, service order information, andreal-time reminder information related to the to-be-notified event, andthe like. The to-be-executed behavior information is information about abehavior that needs to be performed by the user. The operationassociation information includes association information of an operationthat may be performed by the user on the mobile terminal.

In some specific scenario embodiments, for a to-be-notified event abouthotel reservation, a first notification condition is to provide areminder one day before an actual check-in date (reminder contentcorresponding to the first notification condition is related informationindicating that the user is to have a stay in a hotel), and it isdetermined that a second notification condition is to provide a reminderat a specific time on the actual check-in date (reminder contentcorresponding to the second notification condition includes relatedinformation indicating that the user is to check in). In this case, acurrent time is monitored, and a first notification page including firstassociation information is displayed one day before the current timereaches the actual check-in date. The first association informationincludes a reminder provided to the user that a hotel check-in event isto occur on the second day. Information such as a hotel name, a hoteladdress, a room type, a check-in time, a guest name, and a hotel roomfee is also displayed.

In some specific scenario embodiments, for a to-be-notified event aboutflight ticket reservation, a first notification condition is that thereis three hours before an airplane takes off and a current user locationis at a distance of more than 3 kilometers from an airport. When themobile terminal learns through monitoring that a current time is threehours earlier than departure of the airplane and determines that acurrent place is at a distance of more than 3 kilometers from theairport, the mobile terminal determines that the first notificationcondition is met, and therefore triggers a first notification page to bedisplayed. First association information is displayed on the firstnotification page, and the first association information includes areminder that the user needs to set off for the airport. Informationsuch as a flight number, an airline, a departure place and weather ofthe departure place, a landing place and weather of the landing place, adeparture time, a landing time, and a passenger name is also displayed.In addition, reminder information (for example, a reminder of taking ataxi, or taking a subway due to a traffic jam) for a better travelmanner may be provided based on a distance from the current location tothe airport and a time that is left before the departure. In addition,the first association information may further include real-time reminderinformation such as a map including a real-time user location, and atime at which the user is expected to arrive at the airport based on acurrent speed at which the user rushes to the airport.

In some specific scenario embodiments, the first notification pageincludes a departure time, a departure place, an arrival time, and anarrival place on a train ticket, weather of the departure place, weatherof the arrival place, a passenger name, a passenger identity cardnumber, carriage information, seat information, a current stage(including “waiting”, “setting off”, “about to arrive”, and “arrived”),and the like, so that the user does not need to search an SMS message, acorresponding train reservation website, or a corresponding applicationprogram for related information.

A display manner of the second notification page is the same as adisplay manner of the first notification page, and content displayed onthe second notification page and the first notification page may bedifferent based on different notification conditions.

A difference from a prior-art form of an SMS message displayed on a lockscreen is that, the first association information displayed on the firstnotification page can help the user intuitively obtain detailed contentof the to-be-notified event at an appropriate event node, so that theuser can execute event content of the to-be-notified event based on thedetailed content, without further searching for related information byperforming a complex operation.

In some embodiments, in step S203 or step S204, the mobile terminal maydirectly display a corresponding notification page in a notificationinterface in full screen when a notification condition is met.

A display manner of the second notification page may be the same as adisplay manner of the first notification page, and content displayed onthe second notification page and the first notification page may bedifferent based on the second notification condition and the firstnotification condition that are met. In some embodiments, the secondnotification page may be updated and displayed based on the firstnotification page. To ensure notification simplicity, the firstnotification page may be deleted after the second notification page isupdated and displayed based on the first notification page.

In some embodiments, in step S203 or step S204, the mobile terminal mayfirst display a corresponding notification SMS message when the firstnotification condition or the second notification condition is met, andthen display the corresponding first notification page or thecorresponding second notification page through jumping based on anoperation input of the user for the notification SMS message. In thisdisplay manner, the to-be-notified event can be notified to the user ina timely manner, and interference to a preview and an operationperformed by the user in a current interface that is caused by directlydisplaying a notification page can be avoided.

Specifically, in step S203, the mobile terminal displays a notificationSMS message about the first notification page when the firstnotification condition is met, and then displays the first notificationpage through jumping in response to a case in which an operation inputfor the notification SMS message is detected.

Specifically, in step S204, the mobile terminal displays a notificationSMS message about the second notification page when the secondnotification condition is met, and then displays the second notificationpage through jumping in response to a case in which an operation inputfor the notification SMS message is detected.

There may be one or more notification SMS messages displayed in thenotification interface. A quantity of notification SMS messages isdetermined based on a specific to-be-displayed notification page, andthe quantity is not limited.

Based on some embodiments, in some embodiments, when the notificationinterface includes a plurality of notification pages (which may be thefirst notification page, the second notification page, or both the firstnotification page and the second notification page), the plurality ofnotification pages may exist in the notification interface in a form ofa subpage, and a corresponding notification classification identifier isdisplayed in the notification interface. When the user taps anynotification classification identifier, a notification pagecorresponding to the notification classification identifier isdisplayed, and another notification page is hidden.

In the method, further, a notification classification identifier isdisplayed in the notification interface, and the first notification pageor the second notification page corresponding to the notificationclassification identifier is displayed in response to a case in which anoperation input for the notification classification identifier isdetected.

Specifically, step S203 includes step S203 a, step S203 b, and step S203c. In step S203 a, a notification interface is displayed on the display,where the first notification page exists in the notification interfacein a form of a subpage. In step S203 b, a notification classificationidentifier corresponding to the first notification page is displayed inthe notification interface. In step S203 c, in response to a case inwhich an operation input for the notification classification identifieris detected, the first notification page corresponding to thenotification classification identifier is displayed in the notificationinterface, and another subpage of the notification interface is hidden.

Likewise, step S204 includes step S204 a, step S204 b, and step S204 c.In step S204 a, a notification interface is displayed on the display,where the second notification page exists in the notification interfacein a form of a subpage. In step S204 b, a notification classificationidentifier corresponding to the second notification page is displayed inthe notification interface. In step S204 c, in response to a case inwhich an operation input for the notification classification identifieris detected, the second notification page corresponding to thenotification classification identifier is displayed in the notificationinterface, and another subpage of the notification interface is hidden.

The notification classification identifier is displayed in thenotification interface, and the event display page corresponding to thenotification classification identifier can be displayed in full screenthrough jumping based on the operation input of the user. Thenotification classification identifier may be a notification list or aclassification icon. The notification list may be a strip display bar ina form of an SMS message, and the classification icon may be aclassification icon displayed based on an event type. The notificationclassification identifier is used to briefly remind a user that there iscurrently a notification and is used for switching between differentevent display pages, and the event display page corresponding to thenotification classification identifier can be displayed in full screenthrough jumping based on the operation input of the user. If the currentnotification interface includes a plurality of to-be-displayed eventdisplay pages, the user may perform switching between different eventdisplay pages by tapping different notification classificationidentifiers, to avoid message omission.

In some embodiments, the notification interface includes any one or acombination of the following: a lock screen and/or a notificationclassification display interface on an unlock screen. Persons skilled inthe art should understand that another notification interface applicableto the present disclosure, for example, a three-dimensional virtualreality projection image, can be incorporated herein by reference. Thelock screen is used as an example. When the mobile terminal (forexample, a mobile phone or a tablet computer) is in a screen lockedstate, an updated lock screen is displayed, to provide a notificationreminder to the user.

In some embodiments, when the notification interface is a lock screen,when a message needs to be pushed, the mobile terminal in a screen-offstate triggers the lock screen to be lighted up, and displays updateddisplay content on the lock screen, including displaying the eventdisplay page in full screen or displaying the notificationclassification identifier and the event display page corresponding tothe notification classification identifier. If the mobile terminal iscurrently in a screen-on state when the screen is locked, the currentlock screen may also be updated based on a triggered push message, andupdated display content may be displayed.

In some embodiments, if the mobile terminal is in an unlocked state anda current display interface is not in the notification interface, themobile terminal generates a corresponding notification SMS message basedon the event display page, displays a notification bar in the currentdisplay interface, and displays the notification SMS message on thenotification bar. The notification SMS message can be used to displaythe corresponding event display page through jumping based on theoperation input of the user.

For different notification interfaces, different display manners or acombination of a plurality of display manners may be used, so as toprovide a plurality of message push manners and search manners to theuser.

For example, when the notification interface is a lock screen, it isdetermined whether the mobile terminal is currently in a screen lockedstate. If yes, a quantity of event display pages on the current lockscreen is determined. If there is only one event display page, thecorresponding event display page is directly displayed on the lockscreen in full screen. If there are a plurality of event display pages,notification classification identifiers corresponding to the pluralityof event display pages are displayed in a form of a message list, theuser may perform an input operation (such as tapping or flicking) on thenotification classification identifier in the screen locked state, andan event display page corresponding to the notification classificationidentifier is directly displayed in full screen through jumping in thescreen locked state based on the input operation. The user may furtherreturn to the lock screen including the notification classificationidentifier from the event display page, and tap another notificationclassification identifier to jump to another corresponding event displaypage.

For another example, the notification interface is a notificationclassification display interface. It is determined whether the mobileterminal is currently in the notification classification displayinterface. If yes, a quantity of event display pages in the notificationclassification display interface is determined. If there is only oneevent display page, the corresponding event display page is directlydisplayed in the notification classification display interface in fullscreen. If there are a plurality of event display pages, notificationclassification identifiers corresponding to the plurality of eventdisplay pages are displayed in a form of a message list, the user mayperform an input operation (such as tapping or flicking) on thenotification classification identifier in the notificationclassification display interface, and an event display pagecorresponding to the notification classification identifier is displayedin full screen through jumping in a screen locked state based on theinput operation. The user may further return to the notificationclassification identifier interface from the event display page, and tapanother notification classification identifier to jump to anothercorresponding event display page.

Certainly, a combination of several notification interfaces may be usedto display a notification. For example, when the user is in an unlockedstate and is in another interface, when information needs to be pushed,a notification bar may pop up in the current interface, and anotification SMS message with brief message content may be displayed onthe notification bar. The user may tap the reminder message to display,in full screen through jumping, an event display interface correspondingto the notification SMS message, or directly jump to a notificationclassification display interface including the event display page.

Herein, the lock screen is an interface displayed when a screen of themobile terminal is lighted up but the mobile terminal is still in ascreen locked state. The notification classification display interfaceis an interface that is exclusively used by the mobile terminal todisplay a notification, and includes but is not limited to anotification interface that pops up when the user performs a flick-downoperation from the top of the screen in a desktop interface, and thelike. The notification bar is a notification interface opened by theuser in a current interface, and disappears after notification. Forexample, when there is a to-be-notified message, a strip notificationbar pops up from the top of the screen in the current interface, and thenotification bar does not cover much of the current interface, anddisappears after a period of time (for example, three seconds).

In the foregoing embodiment, in the method, when the mobile terminal iscurrently in another interface, a notification is generated, and arelated reminder message pops up in a form of a notification bar. Afterthe user performs a selection operation such as tapping on the remindermessage, a corresponding notification interface is displayed throughjumping, so as to facilitate a user operation and notify notificationcontent in a timely manner.

In some embodiments, the notification page may include a title region,at least one information reminder region, and an action region. Theinformation reminder region is used to display notification details ofan event. In the information reminder region, an interface of a relatedapplication may be invoked and displayed. For example, permission for amap application is obtained, and a map application interface isdisplayed in the information reminder region, to prompt a user withrelated location information; or permission for a live application isobtained, and current live content is displayed in the informationreminder region. The information reminder region may include a primaryinformation reminder region and an additional information reminderregion. For example, the primary information reminder region may be usedto notify primary information of a current to-do item, including aprimary behavior that needs to be performed by the user, for example,“currently need to set off” or “currently need to check in at anairport”. The additional information reminder region may be used tonotify related information of the to-do item, for example, a ticketnumber, passenger information, or a seat number. In this case, the usermay directly obtain related information of a current service on anotification page, without further searching a corresponding website,application, or SMS message.

In a preferred example, when there is only one notification page, thenotification page is updated to the notification interface in fullscreen, and the notification page occupies the entire notificationinterface. In other words, the notification page is directly displayedto the user in a form of a large image. The notification page candisplay notification details to the user. If there are a plurality ofnotification pages, classification icons and a correspondence between aclassification icon and a notification page are established in a form ofa switchable subpage. When the user taps one of the classificationicons, a corresponding notification page is still displayed in thenotification interface in full screen. In other words, the notificationpage is displayed in a form of a large image.

In some embodiments, in the method, the mobile terminal may furtherupdate a corresponding notification condition and a correspondingnotification page based on an update event of the to-be-notified event.

Specifically, based on the method shown in FIG. 2, the method furtherincludes step S205, step S206, and step S207.

In step S205, the mobile terminal obtains an update event of theto-be-notified event. In step S206, the mobile terminal updates thefirst notification condition and/or the second notification conditionbased on the update event. In step S207, the mobile terminal updates thecorresponding currently displayed first notification page and/or thecorresponding currently displayed second notification page based on theupdated first notification condition and/or the updated secondnotification condition.

In some embodiments, the update event may be determined in the pushmessage and/or the user operation record. The push message and/or theuser operation record are or is obtained, and content of the pushmessage and/or the user operation record is analyzed to determinewhether the content is related to an update event of a to-be-notifiedevent.

Content of a process of obtaining and analyzing the push message and/orthe user operation record to obtain the update event is the same as orbasically the same as that of a process of obtaining the to-be-notifiedevent in the foregoing embodiments. For brevity, details are notdescribed again.

When the update event is obtained, it is determined, based on the updateevent, whether each notification condition corresponding to theto-be-notified event and each notification page that is being displayedneed to be updated.

In some specific scenario embodiments, when receiving an SMS messageabout a flight delay, the mobile terminal finds a correspondingto-be-notified event about flight ticket reservation based on the SMSmessage, and updates each notification condition of the to-be-notifiedevent based on the SMS message, for example, updates a flight departuretime and a landing time in the notification condition. If a notificationpage is currently being displayed, the mobile terminal needs to updatethe flight departure time, the landing time, and the like on thenotification page based on the SMS message, or update event statusinformation on the notification page to “flight delay”, and mark anestimated delay event, and so on.

In some specific scenario embodiments, when detecting that the userperforms a vehicle ticket changing operation in a third-partyapplication, the mobile terminal determines an update event based on theoperation behavior, finds a corresponding to-be-notified event aboutvehicle ticket reservation based on the update event, and updates eachnotification condition of the corresponding to-be-notified event, forexample, updates a departure time, an arrival time, and vehicle ticketinformation in the notification condition. If a notification page iscurrently being displayed, the mobile terminal needs to update thedeparture time, the arrival time, the vehicle ticket information, andthe like on the notification page based on the SMS message, or updateevent status information on the notification page to “changed”, and markchanging related information, and so on.

In some embodiments, based on the method in FIG. 2, the method furtherincludes step S208 and step S209. In step S208, the mobile terminaldetermines a notification cleaning condition based on the to-be-notifiedevent, where the notification cleaning condition includes at least anyone of the following: a cleaning time condition, a cleaning placecondition, and a cleaning user behavior condition. In step S209, themobile terminal deletes the currently displayed first notification pageor the currently displayed second notification page of theto-be-notified event when the notification cleaning condition is met.

The cleaning time condition may be a time condition for completing theto-be-notified event, the cleaning place condition may be a placecondition for completing the to-be-notified event, and the cleaning userbehavior condition may be a cleaning operation (for example, anoperation of tapping “Clean”) to be performed by the user on the mobileterminal.

After determining the notification cleaning condition, the mobileterminal monitors a related condition parameter, including a currenttime, a current place, current user behavior information, and the like,based on the notification cleaning condition. When the notificationcleaning condition is met, the mobile terminal deletes the currentlydisplayed first notification page or the currently displayed secondnotification page of the to-be-notified event. In some embodiments, themobile terminal may also delete a corresponding notification SMS messageor notification classification icon when cleaning the notification page.

In some specific scenario embodiments, if the current time is later thana landing time of an airplane and the user has successfully arrived at adestination by air to complete the flight, the mobile terminaldetermines whether the real-time environment information meets thenotification cleaning condition, and the mobile terminal deletes thecorresponding notification page in the notification interface, to keepthe notification interface clear and concise.

In the prior art, a mobile terminal flashes a notification on the top ofa mobile phone screen or displays a notification in a strip bar onlywhen an event occurs in a service application. In comparison, in themethod provided in the present disclosure, each notification conditionof a to-be-notified event is determined; event information of theto-be-notified event is collected; it is determined, based on contextanalysis on the event information, whether to trigger a notification tobe pushed to the user; and association information of event details ofthe event information is updated to a notification interface in fullscreen in a form of an event display page when it is determined that anotification needs to be pushed. Specifically, an existing event displaypage is updated or a new notification page is created depends on whetherthe notification interface includes a corresponding notification page.In this way, when the event changes, the user can obtain a notificationin a timely manner, and conveniently obtain notification details of theevent from a corresponding notification page in the notificationinterface based on a user requirement, without further searching an SMSmessage or an application.

FIG. 3 is a schematic structural diagram of an apparatus for pushing anotification on a terminal device with a screen according to someembodiments. The apparatus includes an obtaining module, a determiningmodule, a first display module, and a second display module.

The obtaining module obtains a to-be-notified event, where theto-be-notified event is an event for which a notification needs to bepushed to a user. The determining module determines a first notificationcondition and a second notification condition based on theto-be-notified event, where the to-be-notified event is an event forwhich a notification needs to be sent to the user, and the firstnotification condition and the second notification condition eachinclude at least any one of the following: a time condition, a placecondition, a user behavior condition, and an environment condition. Thefirst display module displays a first notification page when the firstnotification condition is met, where the first notification page is usedto display first association information of the to-be-notified event,and the first association information includes one or more of eventstatus information, to-be-executed behavior information, and operationassociation information of the to-be-notified event when the firstnotification condition is met. The second display module displays asecond notification page when the second notification condition is metafter the first notification page is displayed, where the secondnotification page is used to display second association information ofthe to-be-notified event, and the second association informationincludes one or more of event status information, to-be-executedbehavior information, and operation association information of theto-be-notified event when the second notification condition is met.

For methods performed by the obtaining module, the determining module,the first display module, and the second display module, respectivelyrefer to content in step S201, step S202, step S203, and step S204 shownin FIG. 2. Details are not described again.

In the prior art, a notification can be pushed based on only simplecontent of a service application. In comparison, in the push apparatusin some embodiments, a plurality of notification conditions aredetermined based on a to-be-notified event, a corresponding notificationpage is pushed when a notification condition is met as the eventdevelops, and content of the notification page includes various types ofassociation information when the notification condition is met.Therefore, notification content corresponding to different eventdevelopment stages of a to-be-notified event can be pushed to the userat the stages in a timely manner, thereby improving notificationeffectiveness.

In some embodiments, the obtaining module obtains a to-be-notified eventby using an obtaining submodule and an analysis module. The obtainingsubmodule obtains a push message and/or a user operation record, and theanalysis submodule analyzes whether content of the push message and/orthe user operation record is related to a to-be-notified event, and ifyes, determines the to-be-notified event.

In some embodiments, for methods performed by the obtaining submoduleand the analysis module, respectively refer to content in step S201 aand step S202 b. Details are not described again.

The determining module determines the first notification condition andthe second notification condition by using a type determining submodule,a node determining submodule, an information determining submodule, aparameter determining submodule, and a condition determining submodule.The type determining submodule determines an event type of theto-be-notified event. The node determining submodule determines a firstnotification node and a second notification node of the to-be-notifiedevent based on the event type. The information determining submodulecollects event information of the to-be-notified event based on theevent type. The parameter determining submodule determines a nodeparameter of the first notification node in the event information, todetermine the first notification condition corresponding to the firstnotification node. The condition determining submodule determines a nodeparameter of the second notification node in the event information, todetermine the second notification condition corresponding to the secondnotification node.

In some embodiments, for methods performed by the type determiningsubmodule, the node determining submodule, the information determiningsubmodule, the parameter determining submodule, and the conditiondetermining submodule, respectively refer to content in step S202 a,step S202 b, step S202 c, step S202 d, and step S202 e. Details are notdescribed again.

The first display module includes: a first monitoring submodule,configured to monitor a corresponding first condition parameter based onthe first notification condition, where the first condition parameterincludes at least any one of the following: a current time, a currentplace, current user behavior information, and current environmentinformation; and a first display submodule, configured to display thefirst notification page when the first condition parameter meets thefirst notification condition.

The second display module includes: a second monitoring submodule,configured to monitor a corresponding second condition parameter basedon the second notification condition, where the second conditionparameter includes at least any one of the following: a current time, acurrent place, current user behavior information, and currentenvironment information; and a second display submodule, configured todisplay the second notification page when the second condition parametermeets the second notification condition.

For methods performed by the first monitoring submodule and the firstdisplay submodule, respectively refer to step S203 a and step S203 b.For methods performed by the second monitoring submodule and the seconddisplay submodule, respectively refer to step S204 a and step S204 b.

A difference from a prior-art form of an SMS message displayed on a lockscreen is that, the first association information displayed on the firstnotification page can help the user intuitively obtain detailed contentof the to-be-notified event at an appropriate event node, so that theuser can execute event content of the to-be-notified event based on thedetailed content, without further searching for related information byperforming a complex operation.

The first display module may directly display the corresponding firstnotification page in the notification interface in full screen when thefirst notification condition is met. The second display module maydirectly display the corresponding second notification page in thenotification interface in full screen when the second notificationcondition is met.

A display manner of the second notification page may be the same as adisplay manner of the first notification page, and content displayed onthe second notification page and the first notification page may bedifferent based on the second notification condition and the firstnotification condition that are met. In some embodiments, the secondnotification page may be updated and displayed based on the firstnotification page. To ensure notification simplicity, the firstnotification page may be deleted after the second notification page isupdated and displayed based on the first notification page.

The first display module includes a second display submodule and a thirddisplay submodule. The second display submodule displays a notificationSMS message about the first notification page when the firstnotification condition is met, and the third display submodule displaysthe first notification page through jumping in response to a case inwhich an operation input for the notification SMS message is detected.

Likewise, the second display module displays a notification SMS messageabout the second notification page when the second notificationcondition is met, and displays the second notification page throughjumping in response to a case in which an operation input for thenotification SMS message is detected.

In some embodiments, the first display module or the second displaymodule may first display the corresponding notification SMS message whenthe notification condition is met, and then display the notificationpage through jumping based on the operation input of the user for thenotification SMS message. For a display manner of the first displaymodule or the second display module, refer to content in step S203 andstep S204 shown in FIG. 2. In this display manner, the to-be-notifiedevent can be notified to the user in a timely manner, and interferenceto a preview and an operation performed by the user in a currentinterface that is caused by directly displaying a notification page canbe avoided.

In some embodiments, the second display module includes an updatesubmodule. The update submodule updates and displays the secondnotification page based on the first notification page when the secondnotification condition is met after the first notification page isdisplayed. The second display module may further include a deletionsubmodule. The deletion submodule deletes the first notification pageafter the second notification page is updated and displayed based on thefirst notification page. The update submodule can reduce resourcesoccupied for generating the notification page, and the deletionsubmodule can ensure notification simplicity.

When the notification interface includes the first notification pageand/or the second notification page, the apparatus displays anotification classification identifier in the notification interface,and displays, in response to a case in which an operation input for thenotification classification identifier is detected, the firstnotification page or the second notification page corresponding to thenotification classification identifier.

Specifically, the first display module includes a first interfacedisplay submodule, a first identifier display submodule, and a firstpage display submodule. The first interface display submodule displaysthe notification interface on the display, where the first notificationpage exists in the notification interface in a form of a subpage. Thefirst identifier display submodule displays, in the notificationinterface, a notification classification identifier corresponding to thefirst notification page. In response to a case in which an operationinput for the notification classification identifier is detected, thefirst page display submodule displays, in the notification interface,the first notification page corresponding to the notificationclassification identifier, and hides another subpage of the notificationinterface.

For processes performed by the first interface display submodule, thefirst identifier display submodule, and the first page displaysubmodule, respectively refer to content in step S203 a, step S203 b,and step S203 c.

Likewise, the second display module includes a second interface displaysubmodule, a second identifier display submodule, and a second pagedisplay submodule. The second interface display submodule displays anotification interface on the display, where the second notificationpage exists in the notification interface in a form of a subpage. Thesecond identifier display submodule displays, in the notificationinterface, a notification classification identifier corresponding to thesecond notification page. In response to a case in which an operationinput for the notification classification identifier is detected, thesecond page display submodule displays, in the notification interface,the second notification page corresponding to the notificationclassification identifier, and hides another subpage of the notificationinterface.

For processes performed by the second interface display submodule, thesecond identifier display submodule, and the second page displaysubmodule, respectively refer to content in step S204 a, step S204 b,and step S204 c.

In some embodiments, the apparatus further includes an event updatemodule, a condition update module, and a page update module. The eventupdate module obtains an update event of the to-be-notified event. Thecondition update module updates the first notification condition and/orthe second notification condition based on the update event. The pageupdate module updates the corresponding currently displayed firstnotification page and/or the corresponding currently displayed secondnotification page based on the updated first notification conditionand/or the updated second notification condition.

For processes performed by the event update module, the condition updatemodule, and the page update module, respectively refer to content instep S205, step S206, and step S207 shown in FIG. 2.

The apparatus further includes a first cleaning module and a secondcleaning module. The first cleaning module determines a notificationcleaning condition based on the to-be-notified event, where thenotification cleaning condition includes at least any one of thefollowing: a cleaning time condition, a cleaning place condition, and acleaning user behavior condition. The second cleaning module deletes thecurrently displayed first notification page or the currently displayedsecond notification page of the to-be-notified event when thenotification cleaning condition is met.

For methods performed by the first cleaning module and the secondcleaning module, refer to content in step S210 and step S209.

A mobile terminal provided in some embodiments includes: a display (insome embodiments, the display includes a touch-sensitive surface and ascreen); one or more processors; a memory; a plurality of applicationprograms; and one or more programs. The one or more programs are storedin the memory and configured to be executed by the one or moreprocessors, the one or more programs include an instruction, and theinstruction is used to execute content in the method shown in FIG. 2 andsome embodiments corresponding to FIG. 2.

Some embodiments provide a computer-readable storage medium storing oneor more programs. The one or more programs include an instruction, andwhen the instruction is executed by a mobile terminal that includes adisplay and a plurality of application programs, the mobile terminalexecutes content in the method shown in FIG. 2 and some embodimentscorresponding to FIG. 2. The display includes a touch-sensitive surfaceand a screen.

Some embodiments provide a graphical user interface on a mobile terminalwith a display apparatus. The graphical user interface includes: Anotification interface is displayed in the graphical user interface.When a first notification condition of a to-be-notified event is met, afirst notification interface is displayed in the notification interface,and first association information of the to-be-notified event isdisplayed. After the first notification page is displayed, when a secondnotification condition is met, a second notification interface of theto-be-notified event is displayed, and second association information ofthe to-be-notified event is displayed.

The first notification page is used to display the first associationinformation of the to-be-notified event, the to-be-notified event is anevent for which a notification needs to be sent to a user, and the firstassociation information includes one or more of event statusinformation, to-be-executed behavior information, and operationassociation information of the to-be-notified event when the firstnotification condition is met. The second notification page is used todisplay the second association information of the to-be-notified event,and the second association information includes one or more of eventstatus information, to-be-executed behavior information, and operationassociation information of the to-be-notified event when the secondnotification condition is met. The first notification condition and thesecond notification condition each include at least any one of thefollowing: a time condition, a place condition, a user behaviorcondition, and an environment condition.

In a process of displaying the first notification page in thenotification interface in response to a case in which the firstnotification condition of the to-be-notified event is met, the userinterface includes: a notification SMS message about the firstnotification page is displayed in response to the case in which thefirst notification condition of the to-be-notified event is met; and thefirst notification page is displayed through jumping in the notificationinterface in response to a case in which an operation input for thenotification SMS message is detected. In this display manner, theto-be-notified event can be notified to the user in a timely manner, andinterference to a preview and an operation performed by the user in acurrent interface that is caused by directly displaying a notificationpage can be avoided. When a current display interface is an interfacedisplayed in an unlocked state in a process of using the mobile terminalby the user, a notification is notified to the user in a form of anotification bar when being triggered, so that the user can obtain thenotification in a timely manner while currently using the mobileterminal is not affected.

In some embodiments, as shown in FIG. 5(a), an interface currentlydisplayed on the mobile terminal is a program home screen. After a newnotification is received, as shown in FIG. 5(b), a reminder pops up on anotification bar, and the user may perform a flick-down operation ortapping to open a trapezoid, to view an event display page of reminderdetails. As shown in FIG. 5(c), the event display page of thecorresponding notification details is displayed in a notificationclassification display interface. The user may open the notificationclassification display interface by pulling down the notification bar.In this case, a sub-interface in which a service type to which the newnotification that just comes belongs is located is displayed by default,and the user may view details of the notification. In addition, anotheroperation manner may be used. For example, the user may double tap, ortouch and hold content of the notification to enter a correspondingapplication.

In another embodiment, as shown in FIG. 5(d), the mobile terminal iscurrently in a screen locked state. When a notification comes or theuser presses an on/off key to light up a screen of the mobile terminal,to light up and display a lock screen. If there is only onenotification, as shown in FIG. 5(f), the notification is displayed onthe lock screen in a form of notification details, and the user mayperform a flick-up operation to close an event display page, and returnto the lock screen in a screen-on state.

In another optional embodiment, as shown in FIG. 5(d), the mobileterminal is currently in a screen locked state. When the mobile terminallights up and displays the lock screen, as shown in FIG. 5(e), anotification SMS message with a notification details summary isdisplayed. An event display page of notification details is displayed inFIG. 5(f) only when the user taps a notification in the summaryinterface. When collapsing the notification, the user returns to thelock screen including the notification SMS message with the notificationdetails summary in FIG. 5(g). When no notification is displayed on thelock screen, this may be shown in FIG. 5(h).

In another embodiment, a notification is displayed on the lock screen ina form of a notification list (namely, list information). As shown inFIG. 5(i), the mobile terminal is in a screen-off state. When anotification comes or the user presses the on/off key to light up thescreen of the mobile terminal, as shown in FIG. 5(j), a lock screenincluding a plurality of notifications is displayed. The user taps oneof the notifications, and in this case, an event display page of thenotification is displayed in FIG. 5(k). The event display page may beopened by performing tapping, a flick-down operation, or the like. Thenthe user may close the event display page by performing an operation, toreturn to the lock screen. The event display page may be closed bytapping a preset “Back” icon, performing a flick-up operation, or thelike. In this case, a displayed interface returns to the notificationlist on the lock screen in FIG. 5(l).

In addition, corresponding notification details are displayed in thenotification classification display interface. The user may view thenotification details by pulling down the notification bar. When pushinga notification is triggered, a new event display page or an updatedexisting event display page and a notification SMS message correspondingto the new event display page or the updated existing event display pageare generated, the notification bar pops up in the current displayinterface, and the notification SMS message is displayed on thenotification bar. The notification bar is a notification interface thatis opened by the user in the current interface.

The notification interface includes the first notification page and/orthe second notification page, the notification interface furtherincludes a notification classification identifier, and the firstnotification page or the second notification page corresponding to anoperation input of the user for the notification classificationidentifier is displayed through jumping in response to the operationinput. The notification classification identifier is a notification listor a classification icon.

In a specific embodiment of the present disclosure, the notificationinterface in the present disclosure may be a lock screen, or aninterface that is used for notification and to which the user can jumpby performing a specified operation on an unlock screen or the lockscreen. During actual use, a combination of a plurality of notificationinterfaces may be used, to ensure that the mobile terminal cansuccessfully send a notification to the user in various states.

The lock screen is an interface that is displayed when the screen of themobile terminal is lighted up again but the mobile terminal is still ina screen locked state after the mobile terminal is locked. When themobile terminal in a standby mode has not received any operationinstruction in a period of time, or the screen is turned off after theuser presses a key of the mobile terminal for turning off the screen,when the user presses an on key of the mobile terminal, taps the screen,or shakes the mobile phone, and performs another related operation, thescreen is lighted up to display the lock screen. In this case, a homescreen or another interface is entered from the displayed lock screenwithout an unlock operation.

The unlock screen is an interface that is displayed when the userperforms a normal operation on the mobile terminal after unlocking thescreen by using a specified unlocking action (for example, performing aflicking operation in a specified region, and entering a correctunlocking password). The interface includes but is not limited to a homescreen, HiBoard, any display interface of a system application, anyinterface of a third-party application, and the like. On the unlockscreen, the notification interface may be a notification classificationdisplay interface (a PAD screen). The notification classificationdisplay interface may be displayed based on a specified operation of theuser. For example, in a current interface (which may be a desktopinterface or an interface after an application is entered, or may be alock screen displayed for unlocking after the screen is lighted up), theuser performs a flick-down operation from the top of the screen of theterminal, and in this case, the notification classification displayinterface occurs. Certainly, persons skilled in the art shouldunderstand that an operation manner of displaying the notificationclassification display interface is merely an example, and anotheroperation manner, for example, a manner of continually shaking themobile terminal twice, can be incorporated herein by reference providedthat the manner is applicable to the present disclosure.

As shown in FIG. 4(a), a notification interface 400 displayed on ascreen of a mobile phone is used as an example. When a message needs tobe pushed, a new event display page is generated or an existing eventdisplay page is updated based on the event information.

In an optional embodiment, the event display page 404 may be displayedin the notification interface 400 in different manners. For example,when there is only one event display page 404, the event display page isseparately displayed in full screen, in other words, the notificationinterface does not include a notification classification identifier 406shown in FIG. 4(a). When there are a plurality of event display pages404, the several event display pages are displayed in a subpageswitching manner, in other words, the notification interface includesthe notification classification identifier 406 shown in FIG. 4(a), and acorresponding event display page 404 is displayed in a form of a largescreen based on a notification classification identifier 406 selected bythe user. Still referring to FIG. 4(a), in a preferred embodiment, theevent display page 404 may include a title region, a primary informationregion, a secondary information region, and an action region.

The notification classification identifier 406 may be shown in FIG.4(a), and is differentiated based on a service type, including but notlimited to SMS, email, music, schedule, express, group buying, ticket,and the like. A display form of the notification classificationidentifier 406 is preferably an icon. A plurality of sub-interfaces ofthe plurality of event display pages 404 are displayed based on theservice type. The user may perform switching between differentsub-interfaces by selecting the notification classification identifier406. As shown in FIG. 4(b), for example, the user is currently in asub-interface of the “SMS” service type, and an “SMS” service typeidentifier 502 is in a highlighted state. When the user taps an“express” service type identifier 504, the interface switches to asub-interface of the “express” service type shown in FIG. 4(c).

Alternatively, the notification classification identifier 406 may bedisplayed in the notification interface in a form of a notificationlist. As shown in FIG. 4(d), the notification interface is a lock screen600, and notifications 602 and 603 are displayed in a form of anotification list. In the notification interface, when the user taps acorresponding notification list, a corresponding event display page maypop up, or a notification classification display interface may bedisplayed through jumping. As shown in FIG. 4(e), when the user taps thenotification 602, an event display page corresponding to thenotification 602 may be displayed through jumping from the current lockscreen 600.

In a specific scenario embodiment, as shown in FIG. 4(f), in anotification interface, a service type is flight ticket. Informationsuch as a trademark of an airline, a flight number, and a push time maybe displayed in a title region. Current service status information “Cancheck in” is displayed in a primary information region. Other servicerelated information such as a departure time and place, weather of thedeparture place, a landing time and place, weather of the landing place,a passenger name, and a seat number is displayed in a secondaryinformation region. An operation that can be performed by the user in acurrent service status is displayed in an action region. For example,the user may access a corresponding service website to check in aftertapping “Check in”.

Still referring to FIG. 4(d), if the mobile terminal is currently on thelock screen 600, two displayed notifications 602 and 603 are displayedin the interface, and a decision module determines, by using datacollected by an information module, that the notification 602 needs tobe cleaned, the existing notification 602 on the lock screen 600 and anevent display page corresponding to the notification 602 are deleted, asshown in FIG. 4(g). Subsequently, if the decision module furtherdetermines that the notification 603 needs to be cleaned, the existingnotification 603 on the lock screen 600 and an event display pagecorresponding to the notification 603 are deleted, there is currently nonotification, and no notification needs to be displayed on the lockscreen, as shown in FIG. 4(h).

As shown in FIG. 6, an apparatus provided in some specific scenarioembodiments may be a data engine (Data Engine) installed on a mobileterminal with a display apparatus, and the data engine may include aninformation engine module, a decision engine module, and a displayengine module.

Preferably, the data engine is installed on a device such as a mobilephone, a tablet computer, or an intelligent wearable device. The mobilephone is used as an example. The data engine collects statuses ofvarious services on the mobile phone (a service applicationcorresponding to the service may not be running), and determines, basedon current context information of a user, whether a message notificationneeds to be pushed to the user. Content of the message notification anda supported interaction operation vary with a context. The messagenotification is directly displayed to the user on a lock screen in aform of a relatively large image. The user may directly view currentservice information on the lock screen by lighting up a screen, or theuser may directly perform some optional interactions on the lock screen.

When an environment change or a user operation is detected, or it isdetected that a notification is pushed from a network or the informationengine module triggers itself to collect event information, theinformation engine module collects data from service applications,including but not limited to SMS, an address book, an instant messagingapplication (including but not limited to WeChat), a sensor, a taxihailing APP (Application, application), a ticket APP (a vehicle ticket,a flight ticket, or a movie ticket), a weather APP, a music APP, a groupbuying APP, a travel APP, and the like, to provide data support forsubsequent behaviors of the decision engine module.

The decision engine module determines whether a current environmentcondition meets a preset condition. If the current environment conditionmeets the preset condition (a time, a place, weather, an environment,and the like), the decision engine module determines to push or updateinformation or cancel information display to the display engine module,determines information that is to be pushed or updated or whose displayis to be canceled, determines an operation that the user is allowed toperform in a current interface (for example, the user is allowed to opentaxi hailing software or open a map in this interface), and determinesan occasion on which information is to disappear.

The decision engine module determines, in the following cases, whetherthe current environment condition meets the preset notificationcondition: The information engine module reports the collected data tothe decision engine module, and the decision engine module determines,based on a service type, that an estimated time corresponding to theservice type arrives (for example, if the user has reserved a flightticket, the decision engine module reminds, one day in advance, the userto check in, and reminds, two hours in advance, the user to go to anairport, where one day or two hours is an estimated time determinedbased on a flight ticket reservation service).

FIG. 7A and FIG. 7B show a detailed notification push process in which adata engine installed on a mobile phone is used as an example accordingto an embodiment of the present disclosure.

Specifically, in step 301, when various events occur in the mobile phonein real time, reports of real-time events such as a new message, anenvironment change, and internal timing are received. The report eventsinclude a new message, a new email, mobile phone environment changeinformation (including but not limited to light, a temperature, anacceleration, gravity, a GPS, and the like that are provided by a sensormodule), an internal timing reminder (a timing reminder that is set by amodule such as a decision engine module), and a user operation behaviorevent (for example, a user hails a taxi, or a user buys a flightticket). The report events trigger an information engine module tocollect event information.

When detecting that the mobile phone receives a new message, a newemail, or the like, the information engine module analyzes content ofthe new message, the new email, or the like, to determine whether a typeof the report event is service-type content. If the type is service-typecontent, the information engine module triggers information collection.When the information engine module detects that the user performs arelated operation in some service applications such as a taxi hailingAPP, a ticket APP (a vehicle ticket, a flight ticket, or a movieticket), a weather APP, a music APP, a group buying APP, and a travelAPP, the information engine module triggers information collection. Inaddition, when an existing service exists on the mobile phone, ato-be-obtained environment parameter is determined based on a servicetype. When the environment parameter changes, the information enginemodule also triggers information collection. In addition, theinformation engine module may periodically trigger informationcollection.

In step 302, the information engine module analyzes the event. Afterbeing triggered by various report events, the information engine moduleanalyzes and determines an event type, and makes analysis based on theevent type. Analyzed content includes but is not limited to a currentuser operation, current environment information, user motioninformation, a current service status, a hardware status, user attributeinformation, and the like. The information engine module determines atleast one notification trigger parameter, and then transmits an analysisresult to the decision engine module for subsequent action decision.

The current environment information includes but is not limited to acurrent time, a current place, environment brightness learned throughanalysis based on information provided by a light sensor, informationindicating that GPS information of the user is converted into alocation, information indicating that a home keyword is converted into aspecific address, and a current transportation means (determined basedon a speed and a posture of the user by using a preset rule). The usermotion information includes but is not limited to a user motiondirection that is learned by a direction sensor through analysis, thespeed of the user that is learned through analysis based on anacceleration, and a user motion status (walking, running, riding,sleeping, stationary, taking a bus, or driving). Service informationincludes but is not limited to ticket information (messages, emails, andthe like related to tickets such as a vehicle ticket, a flight ticket,and a movie ticket), a destination (including a destination entered bythe user in a map analysis program, a place in an SMS message related toflight ticket reservation and hotel reservation, a place of a home or acompany during a commute, or the like), a time of arrival at thedestination (estimated based on a distance between a current userlocation and the destination and a traffic condition), and a servicestatus (flight ticket: check-in, departure, arrival at an airport,luggage storage, and the like; hotel: check-in, unlocking, and the like;train ticket: waiting, about to depart, departure, arrival, and thelike; movie ticket: redemption, seat guidance, and the like; an expressstatus: collected, being delivered, to be picked up, signed, and thelike; and taxi hailing: being dispatched, driver sets off, taxi arrives,travel starts, to pay, and the like). In addition, the user attributeinformation includes but is not limited to a user characteristic (agender, an age, a height, a weight, a nationality, and the like), andthe like.

In step 303, the decision engine module determines whether a servicenotification update condition (namely, a preset notification condition)is met. The decision engine module monitors real-time environmentinformation in the notification trigger parameter based on the analysisresult provided by the information engine module, and determines whetherthe real-time environment information meets any preset notificationcondition for pushing a new notification, updating an originalnotification, cleaning an original notification, or the like (the presetnotification condition includes but is not limited to conditions such asa specific time range, place range, environment status, service status,and user motion status). When the condition is met, the decision enginemodule notifies the display engine module of a decision result,including information such as a notification type (newnotification/notification updating/notification cleaning), a servicetype, a service status, and an operation allowed in a notification.

A specific process in which the display engine module pushes a newnotification, updates a notification, or cleans a notification is asfollows:

In step 304, when a preset time range (for example, the user is remindedto perform online check-in one day before departure), place range (forexample, the user is prompted with hotel information in a hotel range,or the user is reminded to board near an airport), service status(starting to hail a taxi), hardware status (for example, an earphone isinserted or Bluetooth is enabled for music reminding), and the like aremet, a new service reminder is pushed and step 305 is performed to add anew notification and generate a corresponding event display page.

In step 306, when event information corresponding to an existing serviceexists on the mobile phone, a to-be-obtained environment parameter isdetermined based on a service type. When an environment parameter changemeets a notification update trigger condition of the service, forexample, meets a preset time range (for example, the user is reminded,approximately two hours in advance, to set off), place range (forexample, the user is prompted with a luggage carousel when arriving at adestination airport), or service status (for example, the user has beenon a taxi), new content is pushed to replace an original reminder, andstep 307 is performed to update original notification display content,in other words, update a corresponding event display page.

In step 308, when event information corresponding to an existing serviceexists on the mobile phone, a to-be-obtained environment parameter isdetermined based on a service type. When an environment parameter changemeets a notification cleaning trigger condition of the service, forexample, meets a specific time range (for example, a taxi hailingnotification automatically disappears 10 minutes after a fee for taxihailing has been paid and the user has not confirmed the payment), placerange (for example, a flight ticket notification automaticallydisappears when the user leaves a destination airport), or servicestatus (for example, a notification disappears after the user gets outof a taxi, completes payment, and confirms the payment), step 309 isperformed to clean original notification display content.

The display engine module dynamically displays information to the useraccording to a specific interaction specification based on informationpushed by the decision system.

In a preferred embodiment, the interaction specification is as follows:After step 305 and step 307, step 310 is performed to determine whetherthe mobile phone is currently in a screen locked state. If yes, step 311is further performed to determine whether there is only one eventdisplay page. If yes, step 312 is performed to display notificationdetails of the time on a lock screen in full screen and display thenotification in a notification classification display interface. Ifthere are a plurality of event display pages in step 311, step 313 isperformed to generate, on the lock screen based on the plurality ofdisplay pages, the plurality of event display pages and classificationicons that are used for display switching and that correspond to theevent display pages, display the notifications in a form of anotification list, and also display the notifications in a notificationclassification display interface. If it is determined in step 310 thatthe mobile phone is currently in an unlocked state and is not in ascreen locked state, step 314 is performed to display the notificationsin a notification classification display interface and also display areminder message on a notification bar.

FIG. 8(a) to FIG. 8(h) are schematic diagrams of an interface forpushing a notification at each stage according to an embodiment of afirst specific scenario in the present disclosure. With reference toFIG. 6 and FIG. 7A and FIG. 7B, the following describes a notificationpush process by using an event of taking an airplane after a flightticket is successfully reserved as an example according to theembodiment of the specific scenario provided in the present disclosure.

In step 301, an information engine module detects that a mobile phonereceives a new message or a new email, and analyzes information in thenew message or the new email, to determine that the information isservice-type content and a service type is ticket, and specifically,flight ticket. Alternatively, in step 301, an information engine moduledetects that a user has performed an operation such as reservation orcollection in a ticket application (for example, a flight ticketreservation application). In this case, the information engine module istriggered to collect event information. Specifically, the informationengine module collects the event information based on a flight ticketreservation SMS message, ticket information collected by the user, aflight ticket email reminder, or the like.

In step 302, the information engine module analyzes the eventinformation, seeks specific flight information from a cooperativeservice provider (for example, an airline or a flight ticket reservationapplication) based on information such as a flight number and a date inthe event information, and determines the ticket information.Information about a flight ticket reserved for the user specificallyincludes the flight number, a departure place, a destination, adeparture time, a landing time, a passenger name, an identity cardnumber, a departure airport, a destination airport, the airline, and thelike. The information engine module transmits a result of analyzing theevent information to a decision engine module for subsequent actiondecision.

In step 303, the decision engine module determines, through analysis,whether the analysis result meets a preset service notificationcondition. The decision engine module sets an internal timing reminderbased on the collected flight departure time and an advance (forexample, 24 hours before the departure time). When the timing arrives,the decision engine module further determines, based on real-timeinformation collected by the information engine module, that the usercan check in online for a reserved flight, and determines that a presetservice place notification condition is met. In this case, the decisionengine module pushes notification details of a check-in reminder to adisplay engine module.

Then the display engine module displays, to the user according to aninteraction specification, the notification details pushed by thedecision engine module.

With reference to FIG. 8(a), the display engine module may display thenotification details on a lock screen in a screen locked state. Themobile phone is currently in a screen locked state, and therefore anevent display page is displayed on the lock screen in full screen in aform of notification details. The event display page includesinformation such as the flight number, a flight state “can check in”,the departure time, the departure place, the landing time, a landingplace, weather of the departure place, weather of the landing place, thepassenger name, and a seat number. In addition, the event display pageincludes an action region “Check in”. After tapping “Check in” in theaction region, the user can perform a check-in operation on acorresponding website or application.

In addition, for example, when a notification classification interfaceincludes a plurality of event display pages of notification details,with reference to FIG. 8(b), a reminder is provided throughclassification display, and several classification icons are displayedbelow the event display page. Each classification icon corresponds toone event display page, and when the user taps a classification icon of“Airplane”, an event display page about a flight ticket shown in FIG.8(b) is displayed through jumping from the lock screen.

When an event display page about a flight ticket service exists on thelock screen of the mobile phone, the information engine module collectsa corresponding notification push trigger parameter, includingenvironment parameters “time” and “place”, based on the service type.The decision engine module performs determining based on real-timeenvironment information in the collected notification push triggerparameter, where the real-time environment information includes acurrent time, a user place (determined based on a GPS, an operatornetwork, and Wi-Fi), and a time (estimated based on a map and a roadcondition) required from the current place to the airport.

The following shows a schematic diagram of an interface at each reminderstage in an event development process by using a specific scenarioexample.

(1) Arrival reminder: As shown in FIG. 8(c), when a period of time thata current time is earlier than the departure time is less than or equalto an estimated travel time plus a security check time (for example, 40minutes) plus a time and space advance (for example, in China, theadvance is calculated as 30 minutes in Beijing, Shanghai, Guangdong, orShenzhen, and 10 minutes in other cities), the decision engine moduledetermines that a preset service notification condition is met, pushes adeparture reminder to the display engine module, and recommendsoperation options such as a taxi hailing option (a taxi hailingoperation is not displayed after the user falls within a 5 km range ofthe airport) and a check-in option in the action region. Because theevent display page about the flight ticket event exists, the displayengine module may directly modify the event display page, and update anupdated event display page to the lock screen. If the mobile phone iscurrently in a screen locked state, step 312 is performed to display thenotification on the lock screen in full screen in a form of notificationdetails, as shown in FIG. 8(c), or display the notification in thenotification classification display interface in a form of notificationdetails, as shown in FIG. 8(d).

(2) Arrival reminder: As shown in FIG. 8(e), when the information enginemodule collects user location information by using the GPS, the operatornetwork, Wi-Fi, and the like, and determines, based on the collectedlocation information and flight ticket information, that a user locationfalls within a 5 km range of the departure airport and a current time istwo hours earlier than the airplane departure time, the decision enginemodule determines that a preset service notification condition is met,pushes a boarding reminder to the display engine module, and provides anoperation option for calling an air customer service executive in theaction region. The mobile phone is currently in a screen locked state,and step 312 is performed to display the notification on the lock screenin full screen in a form of notification details, as shown in FIG. 8(e),or display the notification on the lock screen in a form of notificationdetails, as shown in FIG. 8(f).

(3) Luggage storage reminder: As shown in FIG. 8(g), the informationengine module receives a user location change event. The informationengine module may obtain location information of the flight destinationairport based on the collected flight ticket information. Based on userlocation information collected based on the user location, the decisionengine module determines, based on the user location information and theinformation collected by the information engine module, that the usercurrently falls within a range of the destination airport (a 5 km rangeof the airport). The decision engine module determines that a presetservice notification condition is met, and in this case, pushes luggagecarousel information to the display engine module. The mobile phone iscurrently in a screen locked state, and step 312 is performed to displaythe notification on the lock screen in full screen in a form ofnotification details, as shown in FIG. 8(g), or display the notificationon the lock screen or in the notification classification displayinterface in a form of notification details, as shown in FIG. 8(h).

(4) Notification cleaning: When the decision engine module determines,based on the location information of the destination airport that iscollected by the information engine module and current user locationinformation, that the user currently falls beyond the 5 km range of thedestination airport, in step 303, the decision engine module determinesthat a preset service notification condition is met, and specifically, anotification cleaning condition is met in step 308, the decision enginemodule pushes a flight ticket reminder cleaning notification to thedisplay engine module, and the display engine module cleans the flightticket notification. In this case, the user is aware that the flightticket reminder automatically disappears.

Persons skilled in the art should understand that specific descriptionsof the time, the place, the distance, the push content, and the like inthe foregoing embodiment are merely examples helping understanding, andare not limited.

FIG. 9(a) to FIG. 9(d) are schematic diagrams of an interface forpushing a notification at each stage according to an embodiment of asecond specific scenario in the present disclosure. With reference toFIG. 6 and FIG. 7A and FIG. 7B, the following describes a notificationpush process by using an event of checking in at a hotel after a hotelroom is successfully reserved as an example.

In step 301, an information engine module detects that a mobile phonereceives a new message or a new email, and analyzes information in thenew message or the new email, to determine that the information isservice-type content and a service type is travel, and specifically,hotel. Alternatively, in step 301, an information engine module detectsthat a user has performed a reservation operation in a travel APP. Inthis case, the information engine module is triggered to collectinformation. The information engine module obtains, based on a collectedhotel reservation SMS message notification and email notification,information about an event of hotel reservation by the user, and thelike.

In step 302, the information engine module analyzes the eventinformation: The information engine module determines hotel information,including a hotel name and location, a check-in time, a guest name, andthe like, and transmits a result of analyzing the event information to adecision engine module for subsequent action decision.

In step 303, the decision engine module determines whether a presetservice notification condition is met. The information engine modulecollects user location information by using the GPS, the operatornetwork, Wi-Fi, and the like. The decision engine module determines,based on the information collected by the information engine module,that the user falls within a range (for example, a 1 km range) of ahotel, and determines that the preset service notification condition ismet. In this case, the decision engine module pushes hotel reservationinformation to a display engine module. As shown in FIG. 9(a), themobile terminal is currently in a screen locked state, and step 312 isperformed to push notification details of the hotel information to thedisplay engine module.

When an event display page about a hotel service exists on the mobilephone, the information engine module collects corresponding environmentparameters “time” and “place” based on the service type of the event.The decision engine module performs determining based on the mobilephone location information collected by the information engine module byusing the GPS, the operator network, and Wi-Fi, and the collected hotelinformation of the user. The following shows notification content in aninterface at each reminder stage in an event development process.

(1) Unlocking stage: As shown in FIG. 9(b), when determining that theuser currently checks in at the hotel (enters the hotel) on the day ofcheck-in or enters the hotel from the outside within a check-in validityperiod (the user is getting closer to the hotel and enters the hotel),in step 303, the decision engine module determines that a preset servicenotification condition is met, and pushes hotel unlocking information tothe display engine module.

In this case, the display engine module pushes a reminder to the user.If the mobile phone is currently in a screen locked state, step 312 isperformed to display the reminder on a lock screen in a form ofnotification details. When the user touches and holds an unlockingstatus indication icon shown in FIG. 9(c), the interface feeds back“unlocking”, as shown in the following diagram. When the unlocking iscompleted, the unlocking status display icon indicates a completedstate, as shown in FIG. 9(d).

(2) Notification cleaning: When the decision engine module determines,based on information collected by the information engine module, that acurrent service status is “unlocked”, in step 303, the decision enginemodule determines that a preset service notification condition is met,and specifically, determines that a notification cleaning condition ismet in step 308. In this case, the decision engine module pushes a hotelreminder cleaning notification to the display engine module, and thedisplay engine module cleans the hotel notification.

In addition, another scenario reminder may also be provided based on anactual scenario, and details are not described.

FIG. 10(a) to FIG. 10(e) are schematic diagrams of an interface forpushing a notification at each stage according to an embodiment of athird specific scenario in the present disclosure. With reference toFIG. 6 and FIG. 7A and FIG. 7B, the following describes a notificationpush process by using an event of taking a train after a train ticket issuccessfully reserved as an example.

In step 301, an information engine module detects that a mobile phonereceives a new message and a new email, and analyzes information in thenew message and the new email, to determine that the information isservice-type content and a service type is ticket, and specifically,train ticket; and/or (b) the information engine module detects that auser has performed a reservation operation in a ticket APP (theinformation engine module collects a train ticket reservation SMSmessage reminder and email reminder, the user adds the reminder to aticket center, where the ticket center is information about a program ora function in the program for managing various vouchers on a terminal,for example, a pocket function in a Wallet APP or a Dianping APP). Inthis case, the information engine module is triggered to collect timeinformation.

In step 302, the information engine module analyzes the eventinformation: A decision engine module determines, based on the collectedinformation, ticket information, specifically including a train number,a departure city, an arrival city, a departure station, an arrivalstation, a train type, a seat number, a carriage number, a departuredate, a train timetable, a passenger name, and the like, and transmitsan analysis result to the decision engine module for subsequent actiondecision.

In step 303, the decision engine module determines whether a presetservice notification condition is met. In step 303, the decision enginemodule sets a departure event reminder based on the service type, andafter the information engine module receives the event reminder, thedecision engine module determines that the user has currently bought atrain ticket, and determines, based on a current time and a current userlocation (collected by the information engine module), that a conditionthat the user needs to set off to take a taxi (time advance=estimatedtravel time+security check time+ticket check time (40 minutes)+specialadvance (a: 30 minutes in Beijing, Shanghai, Guangdong, and Shenzhen; b:10 minutes in other cities)) is met. In this case, the decision enginemodule pushes a departure reminder, including optional operations andinformation such as ticket information, weather, taxi hailing, and aroute, to a display engine module.

The display engine module may push a notification in a notificationclassification display interface in a form of notification details, asshown in FIG. 10(a).

If a ticket service exists on the mobile phone, the information enginemodule collects corresponding environment parameters “time” and “place”based on the service type. The decision engine module performs decisionbased on collected information (user location information collected bythe information engine module by using the GPS, the operator network,and Wi-Fi, and station location information collected by the informationengine module). The following shows notification content in an interfaceat each reminder stage in an event development process.

(1) Waiting reminder: For example, if the user currently falls within a2 km range of the train station, the user is reminded to wait for thetrain, and a train ticket reminder (including the ticket information) isupdated to the display engine module, as shown in FIG. 10(b).

(2) Departure reminder: The decision engine module determines, based onthe ticket information (including a departure time and the like)collected by the information engine module and a current time, that thetrain has departed. In this case, the decision engine module may push atrain departure reminder to the display engine module, and the displayengine module may display information, as shown in FIG. 10(c).

(3) About-to-arrive reminder: The decision engine module pushes, 15minutes before the train arrives at the destination, an about-to-arrivereminder to the display engine module based on a current time, a currentuser location collected by the information engine module, and traintimetable information. The display engine module may push thenotification, as shown in FIG. 10(d).

(4) Arrival reminder: The decision engine module determines, based onthe ticket information (the train timetable) and the user locationinformation that are collected by the information engine module, thatthe train has currently arrived (the user falls within a 2 km range ofthe train). In this case, the display engine module updates thenotification to an arrival reminder, and provides optional operationssuch as viewing a route and hailing a taxi. The display engine modulepushes the notification, as shown in FIG. 10(e).

(5) Notification cleaning: When the decision engine module determines,based on time information or place information collected by theinformation engine module, that a preset service notification conditionis met, for example, in step 308, a notification cleaning condition ismet after the arrival reminder is existent for 20 minutes or the userhas been away from the train station for 2 kilometers, the decisionengine module pushes a ticket reminder cleaning notification to thedisplay engine module, and the display engine module cleans the flightticket notification. In this case, the user is aware that the ticketreminder automatically disappears.

In addition, another scenario reminder may also be provided based on anactual scenario, and details are not described.

FIG. 11(a) and FIG. 11(b) are schematic diagrams of an interface forpushing a notification at each stage according to an embodiment of afourth specific scenario in the present disclosure. With reference toFIG. 6 and FIG. 7A and FIG. 7B, the following describes a notificationpush process after a movie ticket is successfully reserved.

In step 301, an information engine module detects that a mobile phonereceives a new message, and analyzes information in the new message, todetermine that the information is service-type content and a servicetype is ticket, and specifically, movie ticket; and/or (b) theinformation engine module detects that a user has performed an operationsuch as purchasing in a ticket APP (specifically, a movie ticket), andthe information engine module is triggered to collect event information.

In step 302, the information engine module analyzes an event: Theinformation engine module determines ticket information based on contentin the message, where in this embodiment, the ticket informationincludes a theater name, a movie title, a start time, a theater place, ahall number, a seat number, and the like, and transmits an analysisresult to a decision engine module for subsequent action decision.

When a movie ticket service exists on the mobile phone, the informationengine module collects corresponding environment parameters “time” and“place” based on the service type. When determining, based on thecollected information, that the user arrives at a theater, the decisionengine module determines that a preset service notification condition ismet, and performs notification at each reminder stage in an eventdevelopment process.

(1) Redemption reminder: A movie notification is pushed to a displayengine module. In this embodiment, main content of notification detailsincludes a redeem code, a verification code, and the like. In this case,the user can redeem the code for a movie ticket, as shown in FIG. 11(a).

(2) Seat guidance reminder: The decision engine module pushes a movieticket notification update to the display engine module 10 minutesbefore the opening, to mainly indicate a hall and a seat, as shown inFIG. 11(b).

(3) Notification cleaning: When the decision engine module determines,based on information collected by the information engine module, thatthe user is seated, the decision engine module determines that a presetservice notification condition is met, and specifically, a notificationcleaning condition is met in step 308. In this case, the decision enginemodule pushes a reminder cleaning notification to the display enginemodule, and the display engine module cleans the notification. In thiscase, the user is aware that the notification disappears.

A corresponding reminder is also provided in another abnormal scenario,and details are not described herein.

FIG. 12(a) to FIG. 12(e) are schematic diagrams of an interface forpushing a notification at each stage according to an embodiment of afifth specific scenario in the present disclosure. With reference toFIG. 6 and FIG. 7A and FIG. 7B, the following describes a notificationpush process by using a taxi hailing event as an example.

In step 301, a taxi hailing service exists on a mobile phone.

In step 302, an information engine module analyzes an event: Theinformation engine module collects a user motion status and a currentservice status, and then transmits an analysis result to a decisionengine module for subsequent action decision.

In step 303, the decision engine module determines whether a servicenotification update condition is met: The decision engine moduledetermines that the user is currently hailing a taxi and is in an orderdispatch state, and in this case, the service notification updatecondition is met, and a reminder is pushed to a display engine module.

In step 304, the display engine module displays the reminder to the useraccording to an interaction specification based on time details pushedby the decision system.

(1) Taxi dispatch reminder: The decision engine module determines, basedon collected event information, that a service provider is dispatchingan order, and in this case, a message indicating that an order iscurrently being dispatched is displayed in a notification interface, asshown in FIG. 12(a). An estimated wait event, a distance and a time, anda start place are displayed on an event display page, a place at whichthe user is to get in the taxi is displayed on a map in a displayinterface, and an action region for canceling the call is provided.

(2) Driver departure reminder: When determining, based on the collectedevent information, that the order is successfully dispatched, thedecision engine module pushes a notification, as shown in FIG. 12(b).“Order successfully dispatched” and taxi dispatch information aredisplayed on the event display page, the boarding place of the user or ataxi location is displayed on the map in the display interface, and theaction region for canceling the call is provided.

(3) Taxi arrival reminder: When determining, based on the collectedevent information, that the taxi has arrived at the boarding place, thedecision engine module pushes a notification, as shown in FIG. 12(c).“Arrived at the boarding place” and the taxi dispatch information aredisplayed on the event display page, the boarding place of the user orthe taxi location is displayed on the map in the display interface, andthe action region for canceling the call is provided.

(4) Travel start reminder: After determining, based on the collectedevent information, that the user gets in the taxi, the decision enginemodule pushes a notification, as shown in FIG. 12(d). “Driving” isdisplayed on the event display page, an estimated travel time and travelfee are displayed, and the action region for viewing travel details isprovided.

(5) Payment reminder: When determining, based on collected timeinformation, that a destination is reached, the decision engine modulepushes a notification, as shown in FIG. 12(e). On the event displaypage, a total fee for this travel is displayed on the event displaypage, and the user can tap “OK” in the action region to make acorresponding payment, or the payment is automatically performed inbackground. The reminder automatically disappears after being viewed bythe user or automatically disappears after no operation is performed fora period of time.

A corresponding reminder is also provided in another abnormal scenario,and details are not described herein.

FIG. 13(a) to FIG. 13(g) are schematic diagrams of an interface forpushing a notification at each stage according to an embodiment of asixth specific scenario in the present disclosure. With reference toFIG. 6 and FIG. 7A and FIG. 7B, the following describes a notificationpush process by using an express event as an example.

In step 301, an information engine module detects that a mobile phonereceives a new message, and analyzes information in the new message, todetermine that the information is service-type content and a servicetype is express, and/or the information engine module detects that auser has logistics related information in a shopping APP, and theinformation engine module is triggered to collect information.

In step 302, the information engine module analyzes an event: Theinformation engine module determines information about an expressservice company and logistics status information, and transmits ananalysis result to a decision engine module for subsequent actiondecision.

In step 303, the decision engine module determines whether a servicenotification update condition is met: When there is a change inlogistics information, the decision engine module pushes a notification.As shown in FIG. 13(a), a plurality of notification SMS messages ofexpress information are displayed in a form of a notification list. Whenthe user taps each of the notifications, a corresponding event displaypage is displayed through jumping based on a collected express status,separately shown in FIG. 13(b), FIG. 13(c), FIG. 13d ), FIG. 13(e), FIG.13(f), and FIG. 13(g). Content displayed on the event display pageincludes information such as the express service company, an expressprogress, article delivery details, a pickup place, and a key. Inaddition, operable services, for example, contacting a customer serviceexecutive, ignoring a message, and contacting a courier, are provided inan action region.

A corresponding reminder is also provided in another abnormal scenario,and details are not described herein.

FIG. 14(a) and FIG. 14(b) are schematic diagrams of an interface forpushing a notification at each stage according to an embodiment of aseventh specific scenario in the present disclosure. With reference toFIG. 6 and FIG. 7A and FIG. 7B, the following describes a notificationpush process by using a group buying event as an example.

In step 301, an information engine module detects that a mobile phonereceives a new message, and analyzes information in the new message, todetermine that the information is service-type content and a servicetype is group buying, and/or the information engine module detects thata user has performed an operation such as purchasing in a group buyingAPP, and the information engine module is triggered to collectinformation.

In step 302, the information engine module analyzes an event: Theinformation engine module determines group buying information based oncontent in the message, where in this embodiment, the group buyinginformation includes a store name, a product name, a group buyingvalidity period, store business hours, a store place, and the like, andtransmits an analysis result to a decision engine module for subsequentaction decision.

When a group buying service exists on a mobile phone, the informationengine module collects corresponding environment parameters “time” and“place” based on the service type. When determining, based on thecollected information, that the user arrives at a store, the decisionengine module determines that a service notification update condition ismet, and provides a notification at each stage.

(1) Redemption reminder: A grouping buying coupon notification is pushedto a display engine module, as shown in FIG. 14(a). In this embodiment,the user taps a notification list on a lock screen, to display an eventdisplay page. Main content of notification details on the event displaypage includes a redeem code and the like. In this case, the user canredeem the redeem code for consumption, as shown in FIG. 14(b).

Persons skilled in the art should understand that the foregoingdescriptions of the specific scenarios are only examples intended tohelp understanding, but are not limited to the foregoing embodiments,and specific scenarios of subsequently occurring events that featurecontinuity in which a user needs to be notified, for example, bargainsrush reminding, ticket reservation for a concert, and red envelopegrabbing, can be incorporated herein by reference provided that they areapplicable to the present disclosure.

In conclusion, the foregoing embodiments are merely intended fordescribing the technical solutions of the present disclosure, but notfor limiting the present disclosure. Although the present disclosure isdescribed in detail with reference to the foregoing embodiments, personsof ordinary skill in the art should understand that they may still makemodifications to the technical solutions described in the foregoingembodiments or make equivalent replacements to some technical featuresthereof, without departing from the scope of the technical solutions ofthe embodiments of the present disclosure.

1. A method for pushing a notification on a mobile terminal having adisplay, the method comprising: obtaining an event for which anotification is to be pushed to the terminal; determining a firstnotification condition and a second notification condition based on theevent, wherein each of the first notification condition and the secondnotification condition comprises at least one of a time condition, aplace condition, a behavior condition, or an environment condition;displaying a first notification page on the display when the firstnotification condition is met, the first notification page displayingfirst association information of the event, the first associationinformation comprising one or more of event status information, behaviorinformation, or operation association information of the event when thefirst notification condition is met; and displaying a secondnotification page on the display when the second notification conditionis met, the second notification page displaying second associationinformation of the event, the second association information comprisingone or more of event status information, behavior information, andoperation association information of the event when the secondnotification condition is met.
 2. The method according to claim 1,wherein obtaining an event comprises: obtaining at least one of a pushmessage or a user operation record; analyzing whether content of the atleast one of the push message or the user operation record is related toan event to be notified; and determining the to-be-notified event as theevent for which a notification is to be pushed to the terminal, inresponse to determining that content of the at least one of the pushmessage and the user operation record is related to the to-be-notifiedevent.
 3. The method according to claim 1, wherein determining a firstnotification condition and a second notification condition based on theevent comprises: determining an event type of the event; determining afirst notification node and a second notification node of the eventbased on the event type; collecting event information of the event basedon the event type; determining a node parameter of the firstnotification node in the event information, to determine the firstnotification condition corresponding to the first notification node; anddetermining a node parameter of the second notification node in theevent information, to determine the second notification conditioncorresponding to the second notification node.
 4. The method accordingto claim 1, wherein displaying a first notification page when the firstnotification condition is met comprises: monitoring a first conditionparameter based on the first notification condition, the first conditionparameter comprising at least one of a current time, a current place,current user behavior information, or current environment information;and displaying the first notification page when the first conditionparameter meets the first notification condition.
 5. The methodaccording to claim 1, wherein displaying a first notification page whenthe first notification condition is met comprises: displaying anotification short message service (SMS) message about the firstnotification page; and displaying the first notification page throughjumping in response to a case in which an operation input for thenotification SMS message is detected.
 6. The method according to claim1, wherein displaying a second notification page when the secondnotification condition is met comprises: updating and displaying thesecond notification page based on the first notification page when thesecond notification condition is met.
 7. The method according to claim6, wherein displaying a second notification page when the secondnotification condition is met further comprises: deleting the firstnotification page after the second notification page is updated anddisplayed.
 8. A mobile terminal, comprising: a display; a memoryconfigured to store a computer program; and a processor coupled to thememory configured to execute the computer program to perform operations,the operations comprising: obtaining an event for which a notificationis to be pushed to the mobile terminal; determining a first notificationcondition and a second notification condition based on the event,wherein each of the first notification condition and the secondnotification condition comprises at least one of a time condition, aplace condition, a user behavior condition, or an environment condition;displaying a first notification page on the display when the firstnotification condition is met, the first notification page being used todisplay first association information of the event, the firstassociation information comprising one or more of event statusinformation, behavior information, or operation association informationof the event when the first notification condition is met; anddisplaying a second notification page on the display when the secondnotification condition is met, the second notification page displayingsecond association information of the event, the second associationinformation comprising one or more of event status information, behaviorinformation, or operation association information of the event when thesecond notification condition is met.
 9. The mobile terminal accordingto claim 8, wherein obtaining an event comprises: obtaining at least oneof a push message and a user operation record; analyzing whether contentof the at least one of the push message and the user operation record isrelated to an event to be notified; and determining the to-be-notifiedevent as the event for which a notification is to be pushed to theterminal, in response to determining that content of the at least one ofthe push message and the user operation record is related to theto-be-notified event.
 10. The mobile terminal according to claim 8,wherein determining a first notification condition and a secondnotification condition comprises: determining an event type of theevent; determining a first notification node and a second notificationnode of the event based on the event type; collecting event informationof the event based on the event type; determining a node parameter ofthe first notification node from the event information and determiningthe first notification condition corresponding to the first notificationnode; and determining a node parameter of the second notification nodefrom the event information and determining the second notificationcondition corresponding to the second notification node.
 11. The mobileterminal according to claim 10, wherein displaying a first notificationpage when the first notification condition is met comprising: monitoringa first condition parameter based on the first notification condition,the first condition parameter comprising at least one of a current time,a current place, current user behavior information, or currentenvironment information; and displaying the first notification page whenthe first condition parameter meets the first notification condition.12. The mobile terminal according to claim 8, wherein displaying a firstnotification page when the first notification condition is metcomprises: displaying a notification short message service (SMS) messageabout the first notification page when the first notification conditionis met; and displaying the first notification page through jumping inresponse to a case in which an operation input for the notification SMSmessage is detected.
 13. The mobile terminal according to claim 8,wherein displaying a second notification page when the secondnotification condition is met comprising: updating and displaying thesecond notification page based on the first notification page.
 14. Themobile terminal according to claim 13, wherein displaying a secondnotification page when the second notification condition is metcomprising: deleting the first notification page after the secondnotification page is updated and displayed.
 15. The mobile terminalaccording to claim 8, wherein the operations further comprise: obtainingan update event of the event; updating at least one of the firstnotification condition and the second notification condition based onthe update event; and updating at least one of the first notificationpage or the second notification page currently displayed based on atleast one of the updated first notification condition or the updatedsecond notification condition.
 16. The mobile terminal according toclaim 8, wherein displaying a first notification page on the displaycomprises: displaying a notification interface on the display in a formof a subpage; displaying, in the notification interface, a notificationclassification identifier corresponding to the first notification page;and in response to detection of an operation input for the notificationclassification identifier, displaying, in the notification interface,the first notification page corresponding to the notificationclassification identifier, and suppressing display of anothernotification interface subpage.
 17. The mobile terminal according toclaim 16, wherein the notification classification identifier is anotification list or a classification icon.
 18. The mobile terminalaccording to claim 17, wherein the notification interface is a lockscreen.
 19. The mobile terminal according to claim 8, wherein theoperations further comprise: determining a notification cleaningcondition based on the event, the notification cleaning conditioncomprising at least one of a cleaning time condition, a cleaning placecondition, or a cleaning user behavior condition; and deleting the firstnotification page or the second notification page of the event when thenotification cleaning condition is met.
 20. A graphical user interfaceon a mobile terminal with a display apparatus, comprising: anotification interface displayed on the display apparatus, a firstnotification page displayed in the notification interface in response tosatisfaction of a first notification condition of an event, the firstnotification page displaying first association information of the event,the first association information comprising one or more of event statusinformation, behavior information, or operation association informationof the event; and a second notification page displayed in thenotification interface in response satisfaction of a second notificationcondition of the event, the second notification page displaying secondassociation information of the event, the second association informationcomprising one or more of event status information, behaviorinformation, or operation association information of the event, whereineach of the first notification condition and the second notificationcondition comprises at least one of a time condition, a place condition,a user behavior condition, or an environment condition.